Optional `Deserialize` implementations lacking validation
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
When activating the non-default feature `serialize`, most structs implement `serde::Deserialize` without sufficient validation. This allows breaking invariants in safe code, leading to: * Undefined behavior in `as_string()` methods (which use `std::str::from_utf8_unchecked()` internally). * Panics due to failed assertions. See https://github.com/gz/rust-cpuid/issues/43.
Why it matters now
Fix Fixed raw-cpuid (crates.io): 9.1.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 |
|---|---|---|---|---|---|
| — | raw-cpuid (crates.io) | 3.1.0 to before 9.1.1 | 9.1.1 | Patch available | GHSA-jf5h-cf95-w759 |
- raw-cpuid (crates.io) Vendor— Affected 3.1.0 to before 9.1.1 Fixed in 9.1.1 Patch available GHSA-jf5h-cf95-w759
Remediation
- Fix · GHSA-jf5h-cf95-w759 raw-cpuid (crates.io) Fixed in 9.1.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-jf5h-cf95-w759
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences