libcrux: Potential Panic on Overlong Ciphertext Buffer
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 application that passes in a ciphertext buffer of length greater than `ptxt.len() + TAG_LEN` to `libcrux_chacha20poly1305::encrypt` or `libcrux_chacha20poly1305::xchacha20_poly1305::encrypt` would experience a panic. ## Impact An application where the length of the ciphertext buffer is under attacker control could be made to crash. ## Mitigation The fix makes it so that `libcrux_chacha20poly1305::encrypt` and `libcrux_chacha20poly1305::xchacha20_poly1305::encrypt` no longer panic in this case, but instead write out the ciphertext and tag into the first `ptxt.len() + TAG_LEN` bytes of the provided buffer.
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 |
|---|---|---|---|---|---|
| — | libcrux-chacha20poly1305 (crates.io) | before 0.0.8 | 0.0.8 | Patch available | GHSA-hc3c-63hc-2r9f |
- libcrux-chacha20poly1305 (crates.io) Vendor— Affected before 0.0.8 Fixed in 0.0.8 Patch available GHSA-hc3c-63hc-2r9f
Remediation
- Fix · GHSA-hc3c-63hc-2r9f libcrux-chacha20poly1305 (crates.io) Fixed in 0.0.8 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-hc3c-63hc-2r9f
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences