CVE-2016-20044: PInfo 0.6.9-5.1 contains a local buffer overflow vulnerability that allows local attackers to execute arbitrar
CVE-2016-20044 is a high-severity flaw (CVSS 8.4) affecting pinfo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
PInfo 0.6.9-5.1 contains a local buffer overflow vulnerability that allows local attackers to execute arbitrary code by supplying an oversized argument to the -m parameter. Attackers can craft a malicious input string with 564 bytes of padding followed by a return address to overwrite the instruction pointer and execute shellcode with user privileges.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.4 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 84%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2026-03-28 |
| Last modified | 2026-10-07 |
Last updated 2026-10-07 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2016-20044?
pinfo: upgrade to newer than 0.6.9-5.1. Exact commands for each OS are on this page.
Is CVE-2016-20044 being exploited?
CVE-2016-20044 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-2016-20044 affect?
CVE-2016-20044 affects pinfo. Severity is high (CVSS 8.4). PInfo 0.6.9-5.1 contains a local buffer overflow vulnerability that allows local attackers to execute arbitrary code by supplying an oversized argument to the -m parameter. Attackers can craft a malicious input string with 564 bytes of padd
How urgent is CVE-2016-20044?
Priority 38/100. High severity; Public exploit reference