JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)
- 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
The gose JWT/JWS verification library (its JwtVerifierImpl.Verify component) accepts tokens that contain a `crit` header listing extensions it does not support, when the spec requires such tokens to be rejected. As a result, applications relying on gose to verify JSON Web Tokens may accept tokens they should refuse.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
gose parsed the JWS `crit` header into `JwsHeader.Crit` and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty `crit` should have been rejected — and none were.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- github.com/ThalesGroup/gose
From 0.7.3 · through 0.13.0-rc1
- github.com/eclipse-keypont/gose
fixed in 1.0.0-rc4