JweRsaKeyEncryptionDecryptorImpl.Decrypt panics on attacker-chosen IV length (stdlib GCM.Open reached without nonce-size check)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.0-rc4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
This vulnerability affects the JWE (JSON Web Encryption) decryption component of a Go library that handles RSA key encryption, where a maliciously crafted token with an incorrectly sized initialization vector can cause the decrypting process to panic. The result is a denial-of-service condition, as the crash interrupts the goroutine handling the request.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
`JweRsaKeyEncryptionDecryptorImpl.Decrypt` passed the JWE's initialization vector to `cipher.AEAD.Open` without checking its length. The Go standard library panics rather than returning an error when a GCM nonce is not exactly `NonceSize()` bytes, so a JWE carrying a wrong-sized IV crashes the decrypting goroutine.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- github.com/ThalesGroup/gose
From 0.8.0 · through 0.13.0-rc1
- github.com/eclipse-keypont/gose
fixed in 1.0.0-rc4