GHSA-9gxv-x7rp-r2hc json
gree/jose - "None" Algorithm treated as valid in tokens
published 2y ago modified 3mo ago
- 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
- packagist gree/jose 2.2.1
Is GHSA-9gxv-x7rp-r2hc 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 | gree/jose | <2.2.1 |
2.2.1 |
Classification
References
-
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/gree/jose/2016-08-30.yaml
web
-
github.com
/nov/jose-php
package
-
github.com
/nov/jose-php/compare/2.2.0...2.2.1
web
Sources
- GitHub Advisory GHSA-9gxv-x7rp-r2hc
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.