- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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)
Is RUSTSEC-2024-0449 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | unsafe-libyaml | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.