Crash via out-of-bounds draw_stroke write
Published Sep 23, 2022 · Updated May 23, 2025
Heap-buffer overflow in SWFTools commit 772e55a2 allows context-dependent attackers to crash pdf2swf via a crafted PDF file. During PDF rendering, draw_stroke in lib/gfxpoly/stroke.c writes eight bytes immediately past a heap allocation sized earlier in the same function. The file must be opened with pdf2swf; the demonstrated result is an AddressSanitizer-detected abort, with no confidentiality or integrity impact reported.
Summary
What happened
Heap-buffer overflow in SWFTools commit 772e55a2 allows context-dependent attackers to crash pdf2swf via a crafted PDF file. During PDF rendering, draw_stroke in lib/gfxpoly/stroke.c writes eight bytes immediately past a heap allocation sized earlier in the same function. The file must be opened with pdf2swf; the demonstrated result is an AddressSanitizer-detected abort, with no confidentiality or integrity impact reported.
The record
- CVE
- CVE-2022-35096
- Published
- Sep 23, 2022
- Updated
- May 23, 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 23, 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.
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
- SWFTools pdf2swf draw_stroke crash 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