libcrux Panics During Standalone MAC Operations
Priority LOW 38CWE-125Published · 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
An incorrect constant for the key length in libcrux-poly1305 caused the standalone MAC function `libcrux_poly1305::mac` to always panic with an out-of-bounds memory access. ## Impact Applications wishing to use libcrux-poly1305 as a standalone MAC would experience panics. The use of libcrux-poly1305 in libcrux-chacha20poly1305 is unaffected. ## Mitigation Starting from version `0.0.5`, the correct value is used for the key length constant.
Why it matters now
Fix Fixed libcrux-poly1305 (crates.io): 0.0.5
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 |
|---|---|---|---|---|---|
| — | libcrux-poly1305 (crates.io) | before 0.0.5 | 0.0.5 | Patch available | GHSA-pv9v-5j35-xwcr |
- libcrux-poly1305 (crates.io) Vendor— Affected before 0.0.5 Fixed in 0.0.5 Patch available GHSA-pv9v-5j35-xwcr
Remediation
- Fix · GHSA-pv9v-5j35-xwcr libcrux-poly1305 (crates.io) Fixed in 0.0.5 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pv9v-5j35-xwcr
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences