rustsec-2024-0400
Vulnerability from osv_rustsec
Published
2024-11-28 12:00
Modified
2025-10-28 06:02
Summary
`ruzstd` uninit and out-of-bounds memory reads
Details
Affected versions of ruzstd miscalculate the length of the allocated
and init section of its internal RingBuffer, leading to uninitialized
or out-of-bounds reads in copy_bytes_overshooting of up to 15 bytes.
This may result in up to 15 bytes of memory contents being written into the decoded data when decompressing a crafted archive. This may occur multiple times per archive.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-exposure"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "ruzstd",
"purl": "pkg:cargo/ruzstd"
},
"ranges": [
{
"events": [
{
"introduced": "0.7.0"
},
{
"fixed": "0.7.3"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-x3f4-45xf-rjm7"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions of `ruzstd` miscalculate the length of the allocated\nand init section of its internal `RingBuffer`, leading to uninitialized\nor out-of-bounds reads in `copy_bytes_overshooting` of up to 15 bytes.\n\nThis may result in up to 15 bytes of memory contents being written\ninto the decoded data when decompressing a crafted archive.\nThis may occur multiple times per archive.",
"id": "RUSTSEC-2024-0400",
"modified": "2025-10-28T06:02:18Z",
"published": "2024-11-28T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/ruzstd"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2024-0400.html"
},
{
"type": "REPORT",
"url": "https://github.com/KillingSpark/zstd-rs/issues/75"
},
{
"type": "WEB",
"url": "https://github.com/KillingSpark/zstd-rs/pull/76"
}
],
"related": [],
"severity": [],
"summary": "`ruzstd` uninit and out-of-bounds memory reads"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…