Deserialization functions pass uninitialized memory to user-provided Read
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 passed an uninitialized buffer to a user-provided `Read` instance in: * `deserialize_binary` * `deserialize_string` * `deserialize_extension_others` * `deserialize_string_primitive` This can result in safe `Read` implementations reading from the uninitialized buffer leading to undefined behavior.
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 |
|---|---|---|---|---|---|
| — | messagepack-rs (crates.io) | up to 0.8.1 | — | No fix listed | GHSA-m325-rxjv-pwph |
- messagepack-rs (crates.io) Vendor— Affected up to 0.8.1 Fixed in — No fix listed GHSA-m325-rxjv-pwph
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-m325-rxjv-pwph
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences