# GHSA-255r-3prx-mf99: `rmp-serde` `Raw` and `RawRef` may crash when receiving invalid UTF-8

> An attacker can cause a denial of service by sending invalid UTF-8 data to applications using the rmp-serde library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2022
- **Also known as:** RUSTSEC-2022-0092

## What is GHSA-255r-3prx-mf99?

GHSA-255r-3prx-mf99 is a denial of service vulnerability in rmp-serde, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that `Raw::from_utf8` expects valid UTF-8. If invalid UTF-8 is received it can cause the process to crash.

## Which versions are affected by GHSA-255r-3prx-mf99?

3 open source packages ship an affected version, including rmp-serde.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rmp-serde` | crates.io | All versions | 1.1.1 |
| `rmp-serde` | crates.io | All versions | 1.1.1 |
| `rmp-serde` | crates.io | From 0.0.0-0 | 1.1.1 |

## How do I fix GHSA-255r-3prx-mf99?

Upgrade rmp-serde to 1.1.1 or later.

## Is GHSA-255r-3prx-mf99 being exploited?

There is no known exploitation of GHSA-255r-3prx-mf99 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-255r-3prx-mf99 and fix it if it is affected.

What it is: GHSA-255r-3prx-mf99 is a denial of service vulnerability in rmp-serde, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-255r-3prx-mf99 in the wild and no public exploit code.

Affected packages and fixed versions:
- rmp-serde (crates.io): affected all versions; fixed in 1.1.1
- rmp-serde (crates.io): affected all versions; fixed in 1.1.1
- rmp-serde (crates.io): affected from 0.0.0-0; fixed in 1.1.1

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/GHSA-255r-3prx-mf99/ (Markdown: https://insights.sbomify.com/GHSA-255r-3prx-mf99/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-255r-3prx-mf99

---
From sbomify Insights: https://insights.sbomify.com/GHSA-255r-3prx-mf99/
Summaries are generated and may contain mistakes; the official description above is the record.