no cvss
—
- 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 author of the `lzw` crate is unresponsive.
Maintained alternatives:
- [`weezl`](https://crates.io/crates/weezl)
Patch / fix
- crates.io lzw 0.10.1-0
Is RUSTSEC-2020-0144 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 | lzw | >=0.0.0-0, <0.10.1-0 |
0.10.1-0 |
References
-
crates.io
/crates/lzw
package
-
rustsec.org
/advisories/RUSTSEC-2020-0144.html
advisory
-
github.com
/nwin/lzw/issues/2
report
Sources
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.