# RUSTSEC-2024-0004: `cosmwasm` is unmaintained

> The cosmwasm crate is unmaintained and should be removed from dependencies 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:** No
- **Published:** 20 Jan 2024

## What is RUSTSEC-2024-0004?

RUSTSEC-2024-0004 is a vulnerability in cosmwasm, published on 20 Jan 2024. 

### Official description

The crate `cosmwasm` is [not used anymore] since spring 2020.
The functionality was split in multiple different crates, such as the standard library `cosmwasm-std` and the virtual machine `cosmwasm-vm`. An overview can be found in the [cosmwasm repository].

If you have this crate in your dependency tree, this is very likely by mistake and should be corrected.

[not used anymore]: https://github.com/CosmWasm/cosmwasm/issues/1430
[cosmwasm repository]: https://github.com/CosmWasm/cosmwasm

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

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


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

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

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

## Is RUSTSEC-2024-0004 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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