`simd-json-derive` vulnerable to `MaybeUninit` misuse
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
An invalid use of `MaybeUninit::uninit().assume_init()` in `simd-json-derive`'s derive macro can cause undefined behavior. The original code used `MaybeUninit` to avoid initialisation of the struct and then set the fields using `ptr::write`. The undefined behavior triggered by this misuse of `MaybeUninit` can lead to invlaid memory access and panics in binaries compiled in release mode (aka simd-json-derive prior to version 0.12 has UB and optimizes into some nonsense) The version `0.12.0` removes this section of code, avoiding the use of MaybeUninit alltogether.
Why it matters now
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 |
|---|---|---|---|---|---|
| — | simd-json-derive (crates.io) | before 0.12.0 | 0.12.0 | Patch available | GHSA-pqpw-89w5-82v5 |
- simd-json-derive (crates.io) Vendor— Affected before 0.12.0 Fixed in 0.12.0 Patch available GHSA-pqpw-89w5-82v5
Remediation
- Fix · GHSA-pqpw-89w5-82v5 simd-json-derive (crates.io) Fixed in 0.12.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pqpw-89w5-82v5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences