webp crate may expose memory contents when encoding an image
Priority LOW 38CWE-125Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Affected versions of this crate did not check that the input slice passed to `"webp::Encoder::encode()` is large enough for the specified image dimensions. If the input slice is too short, the library will read out of bounds of the buffer and encode other memory contents as an image, resulting in memory exposure or a segmentation fault. The flaw was corrected in [pull request #44](https://github.com/jaredforth/webp/pull/44) by always validating the input buffer size when constructing the encoder.
Why it matters now
Fix Fixed webp (crates.io): 0.3.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | webp (crates.io) | before 0.3.1 | 0.3.1 | Patch available | GHSA-9q78-27f3-2jmh |
- webp (crates.io) Vendor— Affected before 0.3.1 Fixed in 0.3.1 Patch available GHSA-9q78-27f3-2jmh
Remediation
- Fix · GHSA-9q78-27f3-2jmh webp (crates.io) Fixed in 0.3.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9q78-27f3-2jmh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences