# RUSTSEC-2024-0334: `libp2p-tokio-socks5` is unmaintained

> The libp2p-tokio-socks5 crate is unmaintained, posing potential future security risks due to lack of updates, though no current vulnerabilities are known.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 5 Apr 2024

## What is RUSTSEC-2024-0334?

RUSTSEC-2024-0334 is a vulnerability in libp2p-tokio-socks5, published on 5 Apr 2024. 

### Official description

Note the repository was archived without an issue so we link directly
to the commit that marked the repository as unmaintained.

To the best of the original authors knowledge the crate has no
vulnerabilities as of the last release, it is just unmaintained due to
laziness - new maintainer welcome.

## Which versions are affected by RUSTSEC-2024-0334?

1 open source package ship an affected version, including libp2p-tokio-socks5.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libp2p-tokio-socks5` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2024-0334?

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

## Is RUSTSEC-2024-0334 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2024-0334 and fix it if it is affected.

What it is: RUSTSEC-2024-0334 is a vulnerability in libp2p-tokio-socks5, published on 5 Apr 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0334 in the wild and no public exploit code.

Affected packages and fixed versions:
- libp2p-tokio-socks5 (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-2024-0334/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0334/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2024-0334

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