# RUSTSEC-2019-0032: crust repo has been archived; use libp2p instead

> The crust crate is archived and unmaintained, requiring users to migrate to libp2p to avoid supply chain risks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 21 Nov 2019

## What is RUSTSEC-2019-0032?

RUSTSEC-2019-0032 is a vulnerability in crust, published on 21 Nov 2019. 

### Official description

** The `crust` crate repo was archived with no warning or explanation.**

Given that it was archived with no warning or successor, there's not an
official replacement but [`rust-libp2p`](https://github.com/libp2p/rust-libp2p)
looks like it's got a similar feature set and is actively maintained.

## Which versions are affected by RUSTSEC-2019-0032?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `crust` | crates.io | From 0.0.0-0 | 0.32.2-0 |

## How do I fix RUSTSEC-2019-0032?

Upgrade crust to 0.32.2-0 or later.

## Is RUSTSEC-2019-0032 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2019-0032 and fix it if it is affected.

What it is: RUSTSEC-2019-0032 is a vulnerability in crust, published on 21 Nov 2019. 
Exploitation: There is no known exploitation of RUSTSEC-2019-0032 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2019-0032

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