orx-pinned-vec has undefined behavior in index_of_ptr with empty slices
Priority LOW 38CWE-119Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed orx-pinned-vec (crates.io): 3.21.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | orx-pinned-vec (crates.io) | before 3.21.0 | 3.21.0 | Patch available | GHSA-h5j3-crg5-8jqm |
- orx-pinned-vec (crates.io) Vendor— Affected before 3.21.0 Fixed in 3.21.0 Patch available GHSA-h5j3-crg5-8jqm
Remediation
- Fix · GHSA-h5j3-crg5-8jqm orx-pinned-vec (crates.io) Fixed in 3.21.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-h5j3-crg5-8jqm
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences