Converter crash via invalid Type 3 font write
Published Aug 16, 2022 · Updated Aug 3, 2024
Memory corruption in SWFTools pdf2swf commit 772e55a2 allows context-dependent attackers to crash the converter via a crafted PDF file. InfoOutputDev::type3D0 passes an invalid near-null destination to memset while interpreting a Type 3 font character-width operator. A user must invoke pdf2swf on the crafted file, and the demonstrated consequence is termination of that converter process.
Summary
What happened
Memory corruption in SWFTools pdf2swf commit 772e55a2 allows context-dependent attackers to crash the converter via a crafted PDF file. InfoOutputDev::type3D0 passes an invalid near-null destination to memset while interpreting a Type 3 font character-width operator. A user must invoke pdf2swf on the crafted file, and the demonstrated consequence is termination of that converter process.
The record
- CVE
- CVE-2022-35101
- Published
- Aug 16, 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
- Aug 16, 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.
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.
Public exploit references
- id177_SEGV pdf2swf 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