Converter crash via malformed PCF file
Published Feb 17, 2022 · Updated Aug 3, 2024
Improper PCF file validation in pcf2bdf 1.05 through 1.06 allows local users to crash the converter with a crafted font file. In main at pcf2bdf.cc line 1190, the parser reads an invalid address after partially processing attacker-controlled PCF content. Execution of the file by a user is required, and the resulting segmentation fault interrupts the converter and dependent processing.
Summary
What happened
Improper PCF file validation in pcf2bdf 1.05 through 1.06 allows local users to crash the converter with a crafted font file. In main at pcf2bdf.cc line 1190, the parser reads an invalid address after partially processing attacker-controlled PCF content. Execution of the file by a user is required, and the resulting segmentation fault interrupts the converter and dependent processing.
The record
- CVE
- CVE-2022-23319
- Published
- Feb 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1284, 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.
Weakness, pattern, technique
Public exploit references
- segfault_deadly_signal PCF sampleproof 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