web-token/jwt-encryption
5 known CVEs (4 high, 1 low), with the versions each affects and the releases that fix them.
- Latest release
- Not known: cve.now hasn't read this package's releases
- Newest unaffected release
- Not known without release data
- Downloads on affected versions
- Not known: no per-version downloads for this ecosystem
Advisories 5
- GHSA-JC6J-46G2-XWQCDirect encryption (dir) does not check the key size: with a key of half the required size, AES-CBC-HMAC content is encrypted under an all-zero AES key and anyone holding the token can read itAffected: through 3.2.10.
- GHSA-5CC5-V8QV-6CW7dir, ECDH-ES and ECDH-SS accept a non-empty JWE Encrypted Key, so token strings are malleableAffected: through 3.2.10.
- GHSA-3VQW-452C-G726JWE and JWS loaders try every recipient or signature of a token, so a small token multiplies the PBES2 iteration cap (denial of service)Affected: from 0.5.0, through 3.2.10.
- GHSA-2XQ2-PP89-X7FRJWS and JWE serializers decode attacker-controlled JSON without bounds before verification (CPU and memory denial of service)Affected: through 3.2.10.
- GHSA-J265-MG9Q-WPV9AES-GCM decryption accepts any authentication tag length: a holder of one valid JWE can brute force a 1-byte tag in at most 256 requests and rewrite the plaintextAffected: fixed in 1.2.0.