GHSA-h533-5v22-8vcp json
firebase/php-jwt: "None" Algorithm treated as valid on tokens
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).
Patch / fix
Is GHSA-h533-5v22-8vcp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | firebase/php-jwt | <2.0.0 |
2.0.0 |
References
-
github.com
/firebase/php-jwt/commit/b2c2be6a45fda769c8c2ffe5ec4259a9d1e46e5b
web
-
auth0.com
/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries
web
-
auth0.com
/blog/critical-vulnerabilities-in-json-web-token-libraries
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/firebase/php-jwt/2015-04-02.yaml
web
-
github.com
/firebase/php-jwt
package
Sources
- GitHub Advisory GHSA-h533-5v22-8vcp
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.