Application crash via unchecked RIFF size
Published Jul 28, 2022 · Updated Aug 3, 2024
Out-of-bounds write in png2webp 1.0.4 allows context-dependent attackers to crash the converter via a crafted WebP file. The w2p function trusts the 32-bit RIFF size field, adds eight, and uses the result without rejecting integer wraparound or invalid payload lengths. Processing requires user interaction with a malicious WebP file; public evidence demonstrates a crash and does not establish code execution.
Summary
What happened
Out-of-bounds write in png2webp 1.0.4 allows context-dependent attackers to crash the converter via a crafted WebP file. The w2p function trusts the 32-bit RIFF size field, adds eight, and uses the result without rejecting integer wraparound or invalid payload lengths. Processing requires user interaction with a malicious WebP file; public evidence demonstrates a crash and does not establish code execution.
The record
- CVE
- CVE-2022-36752
- Published
- Jul 28, 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
- Jul 28, 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
- GitHub issue 3 crash fileproof 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