Local crash via out-of-bounds image read
Published Aug 16, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in SWFTools commit 772e55a2 allows local users to crash swfrender by processing a crafted SWF file. In swf_DefineLosslessBitsTagToImage at lib/modules/swfbits.c:1037, image extraction reads four bytes 764 bytes beyond a 256-byte heap allocation. A user must invoke swfrender on the file; the demonstrated result is an abort, with no reported confidentiality or integrity effect.
Summary
What happened
Heap-buffer overflow in SWFTools commit 772e55a2 allows local users to crash swfrender by processing a crafted SWF file. In swf_DefineLosslessBitsTagToImage at lib/modules/swfbits.c:1037, image extraction reads four bytes 764 bytes beyond a 256-byte heap allocation. A user must invoke swfrender on the file; the demonstrated result is an abort, with no reported confidentiality or integrity effect.
The record
- CVE
- CVE-2022-35113
- 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
- swfrender heap-buffer-overflow 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