# RUSTSEC-2020-0051: Obsolete versions of the `rustsec` crate do not support the new V3 advisory format

> Obsolete cargo-audit versions cannot parse new advisory formats, requiring an upgrade to maintain security scanning capabilities.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2020

## What is RUSTSEC-2020-0051?

RUSTSEC-2020-0051 is a vulnerability in rustsec, published on 1 Oct 2020. 

### Official description

If you are seeing this message, you are running an obsolete version of
`cargo-audit` which does not support the new V3 advisory format.
These versions are end-of-life.

This advisory is a notice that that it will soon be unable to parse the
advisory database.

Please upgrade `cargo-audit` to a newer release.

## Which versions are affected by RUSTSEC-2020-0051?

1 open source package ship an affected version, including rustsec.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rustsec` | crates.io | From 0.0.0-0 | 0.19.0 |

## How do I fix RUSTSEC-2020-0051?

Upgrade rustsec to 0.19.0 or later.

## Is RUSTSEC-2020-0051 being exploited?

There is no known exploitation of RUSTSEC-2020-0051 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2020-0051 and fix it if it is affected.

What it is: RUSTSEC-2020-0051 is a vulnerability in rustsec, published on 1 Oct 2020. 
Exploitation: There is no known exploitation of RUSTSEC-2020-0051 in the wild and no public exploit code.

Affected packages and fixed versions:
- rustsec (crates.io): affected from 0.0.0-0; fixed in 0.19.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-2020-0051/ (Markdown: https://insights.sbomify.com/RUSTSEC-2020-0051/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2020-0051

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2020-0051/
Summaries are generated and may contain mistakes; the official description above is the record.