# RUSTSEC-2021-0133: cargo-download is unmaintained

> The unmaintained cargo-download crate produces corrupted crates, requiring developers to switch to standard tools like wget or curl.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Dec 2021

## What is RUSTSEC-2021-0133?

RUSTSEC-2021-0133 is a vulnerability in cargo-download, published on 25 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The cargo download subcommand (via cargo-download crate) is broken and maintainer has disappeared from GitHub and hasn't had any commits for a year. 

Using this downloader will result to corrupted crates.

Maintainer has not responded to maintenance takeover.

Just use wget / curl directly.

## Which versions are affected by RUSTSEC-2021-0133?

1 open source package ship an affected version, including cargo-download.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cargo-download` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2021-0133?

No fix has been published for RUSTSEC-2021-0133 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2021-0133 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2021-0133 and fix it if it is affected.

What it is: RUSTSEC-2021-0133 is a vulnerability in cargo-download, published on 25 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of RUSTSEC-2021-0133 in the wild and no public exploit code.

Affected packages and fixed versions:
- cargo-download (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-2021-0133/ (Markdown: https://insights.sbomify.com/RUSTSEC-2021-0133/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2021-0133

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