RUSTSEC-2016-0007 jwt appears to be unmaintained
Not scored
Published
Check this codebase for RUSTSEC-2016-0007 and fix it if it is affected.
What it is: RUSTSEC-2016-0007 is a vulnerability in jwt, published on 9 Oct 2016.
Exploitation: There is no known exploitation of RUSTSEC-2016-0007 in the wild and no public exploit code.
Affected packages and fixed versions:
- jwt (crates.io): affected from 0.0.0-0; no fix listed
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-0007/ (Markdown: https://insights.sbomify.com/RUSTSEC-2016-0007/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is RUSTSEC-2016-0007?
RUSTSEC-2016-0007 is a vulnerability in jwt, published on 9 Oct 2016.
Official description
Which versions are affected by RUSTSEC-2016-0007?
1 open source package ship an affected version, including jwt.
| Package | Affected | Fixed in |
|---|---|---|
jwt crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2016-0007?
No fix has been published for RUSTSEC-2016-0007 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2016-0007 being exploited?
There is no known exploitation of RUSTSEC-2016-0007 in the wild and no public exploit code.