Encoder crash via stale bit-writer double free
Published Jun 20, 2023 · Updated Feb 13, 2025
Double-free in Google libwebp 0.4.2 through 1.3.0 allows attackers to trigger memory corruption via an encoder error path. EncodeAlphaInternal wipes a temporary bit writer but leaves result->bw pointing to the previous trial buffer when initialization fails. ApplyFiltersAndEncode then frees the stale pointer again; reaching the flaw requires an encoder allocation failure, and the documented outcome is a crash with memory corruption.
Summary
What happened
Double-free in Google libwebp 0.4.2 through 1.3.0 allows attackers to trigger memory corruption via an encoder error path. EncodeAlphaInternal wipes a temporary bit writer but leaves result->bw pointing to the previous trial buffer when initialization fails. ApplyFiltersAndEncode then frees the stale pointer again; reaching the flaw requires an encoder allocation failure, and the documented outcome is a crash with memory corruption.
The record
- CVE
- CVE-2023-1999
- Published
- Jun 20, 2023
- Updated
- Feb 13, 2025
- Vendor
- Product
- libwebp
- Classifications
- CWE-415, CWE-416, T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 20, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=0.4.2 <1.3.0-8-ga486d800
- Affected versionversion=0.4.2 <1.3.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