Go JOSE: Panic during CBC-HMAC processing
- 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 4.1.5
- 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
Go JOSE, a Go library implementing JSON Web Encryption, Signature, and Token standards, is affected when applications decrypt attacker-supplied JWE ciphertext using the A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512 algorithms. The flaw can cause a panic, letting an attacker crash the affected application and deny service.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.5, decrypting untrusted JWE ciphertext with A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512 can pass an empty ciphertext buffer to CBC-HMAC unpadding. Insufficient validation allows the empty buffer to be indexed, causing a panic and denial of service. Applications that decrypt attacker-controlled ciphertext with one of these content-encryption algorithms are affected. This issue is fixed in version 4.1.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-jose go-jose
fixed in 4.1.5
- github.com/go-jose/go-jose/v4Go
fixed in 4.1.5
- github.com/go-jose/go-jose/v3Go
through 3.0.5