Crash and memory disclosure via unchecked PCF read
Published Feb 17, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in pcf2bdf before 1.07 allows local users to crash the converter or expose program memory via a crafted PCF font. In pcf2bdf.cc main, malformed input causes a 40-byte read from a one-byte heap allocation without validation that sufficient data remains. Exploitation requires a user or calling process to pass the crafted font to the local command-line converter; no network service is exposed.
Summary
What happened
Heap-buffer overflow in pcf2bdf before 1.07 allows local users to crash the converter or expose program memory via a crafted PCF font. In pcf2bdf.cc main, malformed input causes a 40-byte read from a one-byte heap allocation without validation that sufficient data remains. Exploitation requires a user or calling process to pass the crafted font to the local command-line converter; no network service is exposed.
The record
- CVE
- CVE-2022-23318
- Published
- Feb 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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
- heap_overflow_read_40b crashing PCF 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