rustsec-2025-0106
Vulnerability from osv_rustsec
Published
2025-10-21 12:00
Modified
2025-10-28 06:02
Summary
Undefined behavior in index_of_ptr with empty slices
Details
The safe function index_of_ptr causes undefined behavior when called with an empty slice.
The issue occurs in the line ptr.add(slice.len() - 1) which underflows when slice.len() is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate undefined behavior.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"orx_pinned_vec::utils::slice::index_of_ptr"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "orx-pinned-vec",
"purl": "pkg:cargo/orx-pinned-vec"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "3.21.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-h5j3-crg5-8jqm"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "The safe function `index_of_ptr` causes undefined behavior when called with an empty slice.\n\nThe issue occurs in the line `ptr.add(slice.len() - 1)` which underflows when `slice.len()` is 0, creating a pointer with a massive offset. According to Rust\u0027s safety rules, creating such a pointer causes immediate undefined behavior.",
"id": "RUSTSEC-2025-0106",
"modified": "2025-10-28T06:02:18Z",
"published": "2025-10-21T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/orx-pinned-vec"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2025-0106.html"
},
{
"type": "REPORT",
"url": "https://github.com/orxfun/orx-pinned-vec/issues/52"
},
{
"type": "WEB",
"url": "https://github.com/orxfun/orx-pinned-vec/pull/53"
}
],
"related": [],
"severity": [],
"summary": "Undefined behavior in index_of_ptr with empty slices"
}
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…