RUSTSEC-2016-0004 libusb is unmaintained; use rusb instead
Not scored
Published
Check this codebase for RUSTSEC-2016-0004 and fix it if it is affected.
What it is: RUSTSEC-2016-0004 is a vulnerability in libusb, published on 10 Sep 2016.
Exploitation: There is no known exploitation of RUSTSEC-2016-0004 in the wild and no public exploit code.
Affected packages and fixed versions:
- libusb (crates.io): affected from 0.0.0-0; fixed in 0.3.1-0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/RUSTSEC-2016-0004/ (Markdown: https://insights.sbomify.com/RUSTSEC-2016-0004/index.md)
The libusb crate is unmaintained, posing supply chain risks; developers should migrate to the maintained rusb crate.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is RUSTSEC-2016-0004?
RUSTSEC-2016-0004 is a vulnerability in libusb, published on 10 Sep 2016.
Official description
The libusb crate has not seen a release since September 2016, and its author
is unresponsive.
The rusb crate is a maintained fork:
Which versions are affected by RUSTSEC-2016-0004?
1 open source package ship an affected version, including libusb.
| Package | Affected | Fixed in |
|---|---|---|
libusb crates.io | From 0.0.0-0 | 0.3.1-0 |
How do I fix RUSTSEC-2016-0004?
Upgrade libusb to 0.3.1-0 or later.
Is RUSTSEC-2016-0004 being exploited?
There is no known exploitation of RUSTSEC-2016-0004 in the wild and no public exploit code.