Interpreter crash via out-of-bounds formatted-output read
Published Nov 8, 2022 · Updated May 1, 2025
Heap buffer overflow in PicoC 3.2.2 allows local users to crash the interpreter by supplying a crafted C source file. During ExpressionParseFunctionCall, StdioBasePrintf reads one byte beyond a heap allocation while interpreting crafted source input. Execution requires a user to open the file or pass it to the command-line interpreter, and the demonstrated consequence is a process abort rather than disclosure or code execution.
Summary
What happened
Heap buffer overflow in PicoC 3.2.2 allows local users to crash the interpreter by supplying a crafted C source file. During ExpressionParseFunctionCall, StdioBasePrintf reads one byte beyond a heap allocation while interpreting crafted source input. Execution requires a user to open the file or pass it to the command-line interpreter, and the demonstrated consequence is a process abort rather than disclosure or code execution.
The record
- CVE
- CVE-2022-44319
- Published
- Nov 8, 2022
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- PicoC StdioBasePrintf heap-overflow reproducerproof of concept · 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