Interpreter crash via unterminated comment heap over-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 processing a crafted C source file. In the affected code, LexSkipComment scans for a block-comment terminator without first stopping at Lexer->End, producing a one-byte heap over-read. Execution requires a local user to run the crafted file through PicoC; the demonstrated consequence is an AddressSanitizer-detected abort.
Summary
What happened
Heap buffer overflow in PicoC 3.2.2 allows local users to crash the interpreter by processing a crafted C source file. In the affected code, LexSkipComment scans for a block-comment terminator without first stopping at Lexer->End, producing a one-byte heap over-read. Execution requires a local user to run the crafted file through PicoC; the demonstrated consequence is an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2022-44321
- 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
- LexSkipComment_heap_overflow.c reproduction fileproof 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