# RUSTSEC-2024-0449: unsafe-libyaml is unmaintained

> The unsafe-libyaml library is unmaintained and archived, requiring users to migrate to safe Rust alternatives to avoid unpatched bugs.

- **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 Mar 2024

## What is RUSTSEC-2024-0449?

RUSTSEC-2024-0449 is a vulnerability in unsafe-libyaml, published on 25 Mar 2024. 

### Official description

The [repository](https://github.com/dtolnay/unsafe-libyaml) was archived by
its owner on 2024-03-25 and is read-only. The last release is 0.2.11
(March 2024).

`unsafe-libyaml` is a machine translation of libyaml's C code into unsafe
Rust (c2rust). Bugs found in it will not be fixed upstream. It is used by
`serde_yaml` (itself deprecated) and by forks such as `serde_yaml_ng`.

## Alternatives

Consider a YAML parser written in safe Rust, for example:

- [saphyr](https://crates.io/crates/saphyr) ([serde-saphyr](https://crates.io/crates/serde-saphyr) for serde users)
- [noyalib](https://crates.io/crates/noyalib)

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

1 open source package ship an affected version, including unsafe-libyaml.


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

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

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

## Is RUSTSEC-2024-0449 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2024-0449 is a vulnerability in unsafe-libyaml, published on 25 Mar 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0449 in the wild and no public exploit code.

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

## Sources

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

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