Local heap-buffer overflow via PNG header parsing
Published Oct 13, 2022 · Updated May 15, 2025
A heap-buffer overflow in SWFTools allows local users to cause a service crash via crafted PNG input processed by png_read_header. The png_read_header path processes attacker-controlled PNG header data and overruns a heap buffer. Local execution and user interaction are required, and the reported consequence is an availability failure without stated confidentiality or integrity impact.
Summary
What happened
A heap-buffer overflow in SWFTools allows local users to cause a service crash via crafted PNG input processed by png_read_header. The png_read_header path processes attacker-controlled PNG header data and overruns a heap buffer. Local execution and user interaction are required, and the reported consequence is an availability failure without stated confidentiality or integrity impact.
The record
- CVE
- CVE-2022-35081
- Published
- Oct 13, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 13, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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
- CVE-2022-35081 proof-of-conceptproof of concept · unverified
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