Application crash via out-of-bounds pixel write
Published Sep 23, 2022 · Updated May 22, 2025
A stack-buffer overflow in SWFTools pdf2swf commit 772e55a2 allows local users to crash the converter via a crafted PDF. ImageStream::getPixel writes a decoded image byte past the four-byte pixBuf stack object while pdf2swf renders the file. Processing the file with pdf2swf is required; the demonstrated consequence is an AddressSanitizer-detected abort, with no reported confidentiality or integrity impact.
Summary
What happened
A stack-buffer overflow in SWFTools pdf2swf commit 772e55a2 allows local users to crash the converter via a crafted PDF. ImageStream::getPixel writes a decoded image byte past the four-byte pixBuf stack object while pdf2swf renders the file. Processing the file with pdf2swf is required; the demonstrated consequence is an AddressSanitizer-detected abort, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2022-35099
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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.
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
- pdf2swf crafted-PDF crash 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