Memory disclosure and crash via truncated VP8X chunk
Published May 21, 2021 · Updated Aug 5, 2024
Out-of-bounds read in Google libwebp before 1.0.1 allows remote attackers to read process memory or crash applications via crafted WebP files. WebPMuxCreateInternal parses a truncated VP8X chunk and calls GetLE24 at offsets 12 and 15 without first verifying that the chunk contains the full VP8X header. Reachability requires an application to pass attacker-controlled WebP container data to the mux parser; the result is memory disclosure or an application crash.
Summary
What happened
Out-of-bounds read in Google libwebp before 1.0.1 allows remote attackers to read process memory or crash applications via crafted WebP files. WebPMuxCreateInternal parses a truncated VP8X chunk and calls GetLE24 at offsets 12 and 15 without first verifying that the chunk contains the full VP8X header. Reachability requires an application to pass attacker-controlled WebP container data to the mux parser; the result is memory disclosure or an application crash.
The record
- CVE
- CVE-2018-25012
- Published
- May 21, 2021
- Updated
- Aug 5, 2024
- Vendor
- Product
- libwebp
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
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.
Weakness, pattern, technique
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