Procps Ng Project maintains procps-ng, a foundational system-monitoring utility widely embedded across Unix and Linux distributions for process inspection and resource reporting. The utility's vulnerability footprint, though sparse, reflects its role in low-level system introspection and its presence in nearly all Unix-like environments; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Procps Ng Project over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2018-1123HIGH procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, | May 23, 2018 | 7.5 | 38 | NO | YES |
CVE-2018-1124HIGH 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 att | May 23, 2018 | 7.8 | 35 | NO | YES |
CVE-2018-1122HIGH procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could ach | May 23, 2018 | 7.0 | 33 | NO | YES |
CVE-2018-1126CRITICAL procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124. | May 23, 2018 | 9.8 | 30 | NO | NO |
CVE-2018-1125HIGH procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. | May 23, 2018 | 7.5 | 25 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Procps Ng Project.
Media articles that mention a CVE ID that affects a product developed by Procps Ng Project — matched by CVE ID, not by vendor name.