JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | Eclipse KeyPont - GOSE | unaffected |
|
||||||
| Eclipse Foundation | Eclipse KeyPont - GOSE | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Eclipse | Keypont-gose |
|
||||||||
| Eclipse | Keypont-gose |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.217% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse keypont-gose |
|
| Vendors & Products |
Eclipse
Eclipse keypont-gose |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11) | |
| Weaknesses | CWE-1288 CWE-20 CWE-347 |
|
| References |
| |
| Metrics |
cvssV4_0
|