Reading on uninitialized memory may cause UB ( `util::read_spv()` )
Priority LOW 38Published · 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
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
Why it matters now
Fix Fixed ash (crates.io): 0.33.1
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 |
|---|---|---|---|---|---|
| — | ash (crates.io) | before 0.33.1 | 0.33.1 | Patch available | GHSA-qj69-c89v-jwq2 |
- ash (crates.io) Vendor— Affected before 0.33.1 Fixed in 0.33.1 Patch available GHSA-qj69-c89v-jwq2
Remediation
- Fix · GHSA-qj69-c89v-jwq2 ash (crates.io) Fixed in 0.33.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-qj69-c89v-jwq2
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences