Heap buffer overflow via PutLE16 out-of-bounds write
Published May 21, 2021 · Updated Aug 5, 2024
Heap-based buffer overflow in Google libwebp before 1.0.1 allows attackers to corrupt process memory during WebP processing. PutLE16 writes a 16-bit little-endian value past the end of an allocated heap buffer while processing attacker-controlled image data. The published record establishes memory corruption, while available upstream material documents no demonstrated code-execution path.
Summary
What happened
Heap-based buffer overflow in Google libwebp before 1.0.1 allows attackers to corrupt process memory during WebP processing. PutLE16 writes a 16-bit little-endian value past the end of an allocated heap buffer while processing attacker-controlled image data. The published record establishes memory corruption, while available upstream material documents no demonstrated code-execution path.
The record
- CVE
- CVE-2018-25011
- Published
- May 21, 2021
- Updated
- Aug 5, 2024
- Vendor
- Product
- libwebp
- Classifications
- CWE-787
- 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