binary_vec_io access memory out-of-bounds in binary_read_to_ref and binary_write_from_ref
Priority LOW 38CWE-120Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
Safe functions accept a single `&T` or `&mut T` but multiply by `n` to create slices extending beyond allocated memory when `n > 1`. These functions use `from_raw_parts` to create slices larger than the underlying allocation, violating memory safety. The binary_vec_io repository is archived and unmaintained.
Why it matters now
Fix No fix listed No fixed version in the sources yet
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 |
|---|---|---|---|---|---|
| — | binary_vec_io (crates.io) | up to 0.1.12 | — | No fix listed | GHSA-wwxp-hxh6-8gf8 |
- binary_vec_io (crates.io) Vendor— Affected up to 0.1.12 Fixed in — No fix listed GHSA-wwxp-hxh6-8gf8
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-wwxp-hxh6-8gf8
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences