Invalid use of `mem::uninitialized` causes `use-of-uninitialized-value`
Priority LOW 38Published · 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
The compression and decompression function used `mem:uninitialized` to create an array of uninitialized values, to later write values into it. This later leads to reads from uninitialized memory. The flaw was corrected in commit b633bf265e41c60dfce3be7eac4e4dd5e18d06cf by using a heap-allocated `Vec` and removing out use of `mem::uninitialized`. The fix was released in v0.3.2 and v1.0.0 Subsequently, the crate was deprecated and its use is discouraged.
Why it matters now
Fix Fixed lzf (crates.io): 0.3.2
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 |
|---|---|---|---|---|---|
| — | lzf (crates.io) | before 0.3.2 | 0.3.2 | Patch available | GHSA-5m39-wx2q-mxg3 |
- lzf (crates.io) Vendor— Affected before 0.3.2 Fixed in 0.3.2 Patch available GHSA-5m39-wx2q-mxg3
Remediation
- Fix · GHSA-5m39-wx2q-mxg3 lzf (crates.io) Fixed in 0.3.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-5m39-wx2q-mxg3
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences