Memory disclosure and service interruption via oversized chunks
Published May 21, 2021 · Updated Aug 4, 2024
Out-of-bounds read in Google libwebp before 1.0.1 allows remote attackers to read process memory or interrupt services via crafted WebP data. The mux reader adds header padding to an unvalidated 32-bit RIFF chunk length, allowing the size calculation to wrap before its bounds check. Processing attacker-controlled WebP data is required; the over-read affects confidentiality or terminates the consuming process, with no reported write primitive.
Summary
What happened
Out-of-bounds read in Google libwebp before 1.0.1 allows remote attackers to read process memory or interrupt services via crafted WebP data. The mux reader adds header padding to an unvalidated 32-bit RIFF chunk length, allowing the size calculation to wrap before its bounds check. Processing attacker-controlled WebP data is required; the over-read affects confidentiality or terminates the consuming process, with no reported write primitive.
The record
- CVE
- CVE-2020-36331
- Published
- May 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- libwebp
- Classifications
- CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libwebp 1.0.1
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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