Vulnerability · RUSTSEC-2024-0449

unsafe-libyaml is unmaintained

Published Mar 25, 2024 · RustSec Rust

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2024-0449. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

No version range is stored. A customer cannot check an installed version against this record.
No vendor fix or required action is stored. Compare the linked advisory before you change production.
EPSS is missing. A missing score is not a low risk.

Severity: Unknown—
Known exploitation: Not in CISA/VulnCheck KEV
EPSS: Awaiting synchronization with FIRST
Remediation: Not established
Affected products: RustSec Rust

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). 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 (itself deprecated) and by forks such as . ## 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)

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix RUSTSEC-2024-0449

Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
- RustSec Advisory DB · crates.io

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2024-0449. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

Mar 25, 2024 · RustSec Advisory DB
Detected
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). 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 (itself deprecated) and by forks such as . ## Alternatives Consider a YAML parser written in safe Rust, for ex

Sources

RustSec Advisory DBVendor advisoryRUSTSEC-2024-0449
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). is a machine translation of libyaml's C code into unsafe Rust (c2rust). Bugs found in it will not be fixed upstream. It i
crates.io

Freshness

Last verified in this catalog Unknown date. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.