Lookup for vulnerable packages by Package URL.
| Purl | pkg:npm/jsonwebtoken@4.2.2 |
| Type | npm |
| Namespace | |
| Name | jsonwebtoken |
| Version | 4.2.2 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | false |
| Next_non_vulnerable_version | null |
| Latest_non_vulnerable_version | null |
| Affected_by_vulnerabilities |
|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-54h7-2gp7-1yb9 |
| vulnerability_id |
VCID-54h7-2gp7-1yb9 |
| summary |
JWT Verification bypass with "none" algorithm
It is possible for an attacker to create his own signed token with any payload he wants and have it considered valid using the "none" algorithm. |
| references |
|
| fixed_packages |
|
| aliases |
GMS-2015-4
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-54h7-2gp7-1yb9 |
|
| 1 |
| url |
VCID-5n9u-avux-mbhx |
| vulnerability_id |
VCID-5n9u-avux-mbhx |
| summary |
Use of a Broken or Risky Cryptographic Algorithm
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family). |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2015-9235, GHSA-c7hr-j4mj-j2w6
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-5n9u-avux-mbhx |
|
|
| Risk_score | null |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:npm/jsonwebtoken@4.2.2 |