Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-1124: procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in fi

57
This month
HIGH 7.8WATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2018-1124 is a high-severity flaw (CVSS 7.8) affecting procps-ng, ubuntu linux, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

Why this priority

  • High severity
  • Public exploit reference
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.9% (top 20%)
CISA exploited listNo
WeaknessCWE-122, CWE-190, CWE-787
Published2018-05-23
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: canonical · debian · procps-ng project · redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

procps-ng project procps-ng UPGRADE
Affected: < 3.3.15
Fixed in: 3.3.15
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy procps-ng || rpm -q procps-ng || procps-ng --version
2. UPGRADE to 3.3.15 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade procps-ng
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade procps-ng
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
canonical ubuntu linux MITIGATE
Affected: 14.04 · 16.04 · 17.10 · 18.04
Fixed in: no fixed release known
Safe to downgrade to: a release before 14.04
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
debian debian linux MITIGATE
Affected: 7.0 · 8.0 · 9.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux MITIGATE
Affected: 6.0 · 7.0 · 7.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux desktop MITIGATE
Affected: 6.0 · 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server MITIGATE
Affected: 6.0 · 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1124?

procps-ng: upgrade to 3.3.15; ubuntu linux: mitigate or apply the listed mitigation; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-1124 being exploited?

CVE-2018-1124 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1124 affect?

CVE-2018-1124 affects procps-ng, ubuntu linux, debian linux. Severity is high (CVSS 7.8). procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes

How urgent is CVE-2018-1124?

Priority 57/100. High severity; Public exploit reference; On your watchlist

Software pages

Ubuntu vulnerabilities · Debian vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.