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 `libusb` crate has not seen a release since September 2016, and its author is unresponsive.
The `rusb` crate is a maintained fork:
https://github.com/a1ien/rusb
Patch / fix
- crates.io libusb 0.3.1-0
Is RUSTSEC-2016-0004 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 | libusb | >=0.0.0-0, <0.3.1-0 |
0.3.1-0 |
References
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.