ntru-rs has unsound FFI: Wrong API usage causes write past allocated area
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
The following usage causes undefined behavior. ```rust let kp: ntru::types::KeyPair = …; kp.get_public().export(Default::default()) ``` When compiled with debug assertions, the code above will trigger a `attempt to subtract with overflow` panic before UB occurs. Other mistakes (e.g. using `EncParams` from a different key) may always trigger UB. Likely, older versions of this crate are also affected, but have not been tested.
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 |
|---|---|---|---|---|---|
| — | ntru (crates.io) | 0.4.3 – 0.5.6 | — | No fix listed | GHSA-fq33-vmhv-48xh |
- ntru (crates.io) Vendor— Affected 0.4.3 – 0.5.6 Fixed in — No fix listed GHSA-fq33-vmhv-48xh
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-fq33-vmhv-48xh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences