`read` on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max)
Priority LOW 38Published · 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
Affected versions of this crate calls a user provided `Read` implementation on an uninitialized buffer. `Read` on uninitialized buffer is defined as undefined behavior in Rust.
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 |
|---|---|---|---|---|---|
| — | bite (crates.io) | up to 0.0.5 | — | No fix listed | GHSA-72r2-rg28-47v9 |
- bite (crates.io) Vendor— Affected up to 0.0.5 Fixed in — No fix listed GHSA-72r2-rg28-47v9
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-72r2-rg28-47v9
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences