Nearform fast-jwt
fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery
fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw serialized public JWK or JWKS JSON as an HMAC secret because src/crypto.js performDetectPublicKeyAlgorithms treats non-PEM strings as symmetric key material. If HS256 is explicitly allowed or inferred, an attacker who knows the exact serialized public-key bytes can use those bytes as an HMAC key and create a token containing arbitrary claims that createVerifier accepts. Serialization ordering or whitespace differences can prevent exploitation, and applications using supported PEM keys with an asymmetric-only algorithm allowlist are not affected. This issue is fixed in version 6.3.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.2.4, < 6.3.0
Fixed in 6.3.0
Mitigation
Upgrade fast-jwt to 6.3.0 or later.
References
- Vendor advisory github.com/nearform/fast-jwt/security/advisori…
- Patch github.com/nearform/fast-jwt/pull/636
- Patch github.com/nearform/fast-jwt/commit/10f9591349…
1 more
- Release notes github.com/nearform/fast-jwt/releases/tag/v6.3…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.