rustsec-2026-0130
Vulnerability from osv_rustsec
Published
2026-05-02 12:00
Modified
2026-05-13 12:34
Summary
Out-of-bounds read/write in `Index` and `IndexMut` implementations
Details
The Index and IndexMut implementations for Caja use unchecked pointer
arithmetic without bounds validation. Creating a Caja with a small key and
then accessing an out-of-range index causes out-of-bounds reads or writes
beyond the allocated memory.
This can be triggered through safe public APIs — the [] indexing operator
on a Caja with an out-of-range index — with no unsafe required from the
caller.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "caja",
"purl": "pkg:cargo/caja"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.3.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "The `Index` and `IndexMut` implementations for `Caja` use unchecked pointer\narithmetic without bounds validation. Creating a `Caja` with a small key and\nthen accessing an out-of-range index causes out-of-bounds reads or writes\nbeyond the allocated memory.\n\nThis can be triggered through safe public APIs \u2014 the `[]` indexing operator\non a `Caja` with an out-of-range index \u2014 with no `unsafe` required from the\ncaller.",
"id": "RUSTSEC-2026-0130",
"modified": "2026-05-13T12:34:44Z",
"published": "2026-05-02T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/caja"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0130.html"
},
{
"type": "REPORT",
"url": "https://github.com/EmanuelGCC/Caja/issues/1"
}
],
"related": [],
"severity": [],
"summary": "Out-of-bounds read/write in `Index` and `IndexMut` implementations"
}
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…