web-token/jwt-library vulnerabilities
JWT library
- Registry
- Composer
- Latest
- 4.2.7
- License
- MIT
4 known advisories
The latest version, 4.2.7, is not affected by any of them. Projects on older versions may be.
composer require web-token/jwt-library:^4.2.7Is your project on an affected web-token/jwt-library?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for web-token/jwt-library
PHP JWT Library: RSA1_5 (RSAES-PKCS1-v1_5) decryption lacks implicit rejection, exposing a Bleichenbacher/Marvin padding oracle
- Affected
- <3.4.10 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.7
- Fixed in
- 3.4.10, 4.0.7, 4.1.7
PHP JWT Framework: JWSVerifier uses algorithm from unprotected header, enabling algorithm confusion attacks
- Affected
- <3.4.10 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.7
- Fixed in
- 3.4.10, 4.0.7, 4.1.7
PHP JWT Library: PBES2-HS*+A*KW unwrap accepts an unbounded p2c iteration count, enabling CPU-amplification denial of service
- Affected
- <3.4.10 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.7
- Fixed in
- 3.4.10, 4.0.7, 4.1.7
PHP JWT Framework: Chacha20Poly1305 key-encryption algorithm discards the Poly1305 authentication tag, performing no authentication on decryption
- Affected
- <3.4.10 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.7
- Fixed in
- 3.4.10, 4.0.7, 4.1.7
Is your web-token/jwt-library version vulnerable?
Which of your client projects still run an old web-token/jwt-library?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.