Local code execution via oversized -m argument
Published Mar 28, 2026 · Updated Mar 28, 2026
Stack-based buffer overflow in Pinfo 0.6.9-5.1 allows local users to execute arbitrary code through an oversized -m argument. Processing the -m argument accepts input long enough to overwrite stack control data; the published exploit uses 564 padding bytes and a chosen return address. The attacker must already be able to run Pinfo locally, and successful exploitation runs shellcode only with that user's privileges.
Summary
What happened
Stack-based buffer overflow in Pinfo 0.6.9-5.1 allows local users to execute arbitrary code through an oversized -m argument. Processing the -m argument accepts input long enough to overwrite stack control data; the published exploit uses 564 padding bytes and a chosen return address. The attacker must already be able to run Pinfo locally, and successful exploitation runs shellcode only with that user's privileges.
The record
- CVE
- CVE-2016-20044
- Published
- Mar 28, 2026
- Updated
- Mar 28, 2026
- Vendor
- Pinfo
- Product
- Pinfo
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2026CVE publishedPublication date reported by the CVE source.
- Mar 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.6.9-5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- PInfo 0.6.9-5.1 Local Buffer Overflowfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo