rustsec-2026-0132
Vulnerability from osv_rustsec
Published
2026-05-02 12:00
Modified
2026-05-13 12:38
Summary
Potential out-of-bounds write via public `Context` fields
Details
The Context struct has all fields public (pub d_len, pub digest, etc.).
External code can directly modify d_len to a value exceeding the digest
vector length. When reset() is subsequently called,
self.digest[self.d_len as usize] = 0 indexes out of bounds, causing an
out-of-bounds write.
This can be triggered through safe code — modifying public Context fields
and then calling reset() — with no unsafe required.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "ssdeep",
"purl": "pkg:cargo/ssdeep"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "The `Context` struct has all fields public (`pub d_len`, `pub digest`, etc.).\nExternal code can directly modify `d_len` to a value exceeding the `digest`\nvector length. When `reset()` is subsequently called,\n`self.digest[self.d_len as usize] = 0` indexes out of bounds, causing an\nout-of-bounds write.\n\nThis can be triggered through safe code \u2014 modifying public `Context` fields\nand then calling `reset()` \u2014 with no `unsafe` required.",
"id": "RUSTSEC-2026-0132",
"modified": "2026-05-13T12:38:12Z",
"published": "2026-05-02T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/ssdeep"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0132.html"
},
{
"type": "REPORT",
"url": "https://github.com/rustysec/fuzzyhash-rs/issues/14"
}
],
"related": [],
"severity": [],
"summary": "Potential out-of-bounds write via public `Context` fields"
}
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…