LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| benmcollins | libjwt | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Benmcollins | Libjwt |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.259% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Benmcollins
Benmcollins libjwt |
|
| Vendors & Products |
Benmcollins
Benmcollins libjwt |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LibJWT is a C JSON Web Token Library. From 3.0.0 to 3.3.2, libjwt accepts an RSA JWK that does not contain an alg parameter as the verification key for an HS256/HS384/HS512 token. In the OpenSSL backend, this causes HMAC verification to run with a zero-length key, so an attacker can forge a valid JWT without knowing any secret or RSA private key. This is an algorithm-confusion authentication bypass. It affects applications that load RSA keys from JWKS where alg is omitted, which is valid JWK syntax and common in real deployments, and then choose the verification algorithm from the JWT header, for example in a kid lookup callback. This vulnerability is fixed in 3.3.3. | |
| Title | LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC | |
| Weaknesses | CWE-327 CWE-347 |
|
| References |
| |
| Metrics |
cvssV4_0
|