GHSA-5m39-wx2q-mxg3 json
Invalid use of `mem::uninitialized` causes `use-of-uninitialized-value`
published 4y ago modified 3y ago also RUSTSEC-2022-0067
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
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.
Patch / fix
Is GHSA-5m39-wx2q-mxg3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | lzf | <0.3.2 >=0.0.0-0, <0.3.2 |
0.3.2 |
References
-
github.com
/badboy/lzf-rs/commit/b633bf265e41c60dfce3be7eac4e4dd5e18d06cf
web
-
github.com
/badboy/lzf-rs/issues/9
web, report
-
github.com
/badboy/lzf-rs
package
-
rustsec.org
/advisories/RUSTSEC-2022-0067.html
web, advisory
-
crates.io
/crates/lzf
package
Sources
- GitHub Advisory GHSA-5m39-wx2q-mxg3
- OSV RUSTSEC-2022-0067
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.