Process crash via out-of-bounds string read
Published Aug 15, 2023 · Updated Oct 8, 2024
Heap buffer overflow in Michael R Sweet codedoc 3.7 allows local users to crash the process by processing a crafted source file. The highlight_c_string function reads one byte before a one-byte heap allocation while syntax-highlighting the supplied content. Exploitation requires codedoc to process attacker-supplied local input; the demonstrated consequence is an abort of the codedoc process.
Summary
What happened
Heap buffer overflow in Michael R Sweet codedoc 3.7 allows local users to crash the process by processing a crafted source file. The highlight_c_string function reads one byte before a one-byte heap allocation while syntax-highlighting the supplied content. Exploitation requires codedoc to process attacker-supplied local input; the demonstrated consequence is an abort of the codedoc process.
The record
- CVE
- CVE-2023-38850
- Published
- Aug 15, 2023
- Updated
- Oct 8, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 2024Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
- poc225 crafted inputproof 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