fast-jwt accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nearform | fast-jwt | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nearform | Fast-jwt |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hm7r-c7qw-ghp6 | fast-jwt accepts unknown `crit` header extensions (RFC 7515 violation) |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.158% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:nearform:fast-jwt:*:*:*:*:*:node.js:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nearform
Nearform fast-jwt |
|
| Vendors & Products |
Nearform
Nearform fast-jwt |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, fast-jwt does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that fast-jwt does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. | |
| Title | fast-jwt accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation) | |
| Weaknesses | CWE-345 CWE-636 |
|
| References |
| |
| Metrics |
cvssV3_1
|