GHSA-H5J3-CRG5-8JQM
Vulnerability from github – Published: 2025-10-21 21:54 – Updated: 2025-10-21 21:54The 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": [
{
"package": {
"ecosystem": "crates.io",
"name": "orx-pinned-vec"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-119",
"CWE-191"
],
"github_reviewed": true,
"github_reviewed_at": "2025-10-21T21:54:27Z",
"nvd_published_at": null,
"severity": "LOW"
},
"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": "GHSA-h5j3-crg5-8jqm",
"modified": "2025-10-21T21:54:27Z",
"published": "2025-10-21T21:54:27Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/orxfun/orx-pinned-vec/issues/52"
},
{
"type": "WEB",
"url": "https://github.com/orxfun/orx-pinned-vec/pull/53"
},
{
"type": "WEB",
"url": "https://github.com/orxfun/orx-pinned-vec/commit/4a4007a1aaff25cd417853c76163883a7110e276"
},
{
"type": "PACKAGE",
"url": "https://github.com/orxfun/orx-pinned-vec"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2025-0106.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P",
"type": "CVSS_V4"
}
],
"summary": "orx-pinned-vec has undefined behavior in index_of_ptr with empty slices"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.