# RUSTSEC-2020-0003: rust_sodium is unmaintained; switch to a modern alternative

> The rust_sodium crate is unmaintained, posing supply chain risks; developers should migrate to sodiumoxide.

- **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:** 20 Jan 2020

## What is RUSTSEC-2020-0003?

RUSTSEC-2020-0003 is a vulnerability in rust_sodium, published on 20 Jan 2020. 

### Official description

The `rust_sodium` crate is no longer maintained by its current owner, who
advise in the repository readme that they are looking for
someone else to take ownership of it.

We recommend you switch to an alternative crate such as:
- [`sodiumoxide`](https://crates.io/crates/sodiumoxide)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rust_sodium` | crates.io | From 0.0.0-0 | 0.10.3-0 |

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

Upgrade rust_sodium to 0.10.3-0 or later.

## Is RUSTSEC-2020-0003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2020-0003 is a vulnerability in rust_sodium, published on 20 Jan 2020. 
Exploitation: There is no known exploitation of RUSTSEC-2020-0003 in the wild and no public exploit code.

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

## Sources

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

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