jsonwebtoken has Type Confusion that leads to potential authorization bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Keats | jsonwebtoken | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Keats | Jsonwebtoken | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-h395-gr6q-cpjc | jsonwebtoken has Type Confusion that leads to potential authorization bypass |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.496% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:keats:jsonwebtoken:*:*:*:*:*:rust:*:* | |
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Keats
Keats jsonwebtoken |
|
| Vendors & Products |
Keats
Keats jsonwebtoken |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | jsonwebtoken is a JWT lib in rust. Prior to version 10.3.0, there is a Type Confusion vulnerability in jsonwebtoken, specifically, in its claim validation logic. When a standard claim (such as nbf or exp) is provided with an incorrect JSON type (Like a String instead of a Number), the library’s internal parsing mechanism marks the claim as “FailedToParse”. Crucially, the validation logic treats this “FailedToParse” state identically to “NotPresent”. This means that if a check is enabled (like: validate_nbf = true), but the claim is not explicitly marked as required in required_spec_claims, the library will skip the validation check entirely for the malformed claim, treating it as if it were not there. This allows attackers to bypass critical time-based security restrictions (like “Not Before” checks) and commit potential authentication and authorization bypasses. This issue has been patched in version 10.3.0. | |
| Title | jsonwebtoken has Type Confusion that leads to potential authorization bypass | |
| Weaknesses | CWE-843 | |
| References |
| |
| Metrics |
cvssV4_0
|