# RUSTSEC-2021-0099: Crate has been renamed to `cosmrs`

> The cosmos_sdk crate was renamed to cosmrs, requiring developers to update dependencies to maintain supply chain integrity.

- **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:** 25 Aug 2021

## What is RUSTSEC-2021-0099?

RUSTSEC-2021-0099 is a vulnerability in cosmos_sdk, published on 25 Aug 2021. 

### Official description

The `cosmos_sdk` crate, which provides a basic Rust SDK for the Cosmos ecosystem,
has rebranded to “CosmRS” in the spirit of other projects like CosmJS and CosmWasm.

You can find the new home here:

https://github.com/cosmos/cosmos-rust/tree/main/cosmrs

The new crate name is `cosmrs`:

https://crates.io/crates/cosmrs

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

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


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

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

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

## Is RUSTSEC-2021-0099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2021-0099 is a vulnerability in cosmos_sdk, published on 25 Aug 2021. 
Exploitation: There is no known exploitation of RUSTSEC-2021-0099 in the wild and no public exploit code.

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

## Sources

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

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