Cisco node-jose improper validation of JWT signature
A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-0114US | high7.5 | Exploit | ||
A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the t… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/cisco/node-josePACKAGE
- https://github.com/cisco/node-jose/blob/master/CHANGELOG.mdWEB
- https://github.com/zi0Black/POC-CVE-2018-0114WEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-0114ADVISORY
- https://tools.cisco.com/security/center/viewAlert.x?alertId=56326WEB
- https://web.archive.org/web/20210124130907/http://www.securityfocus.com/bid/102445WEB
- https://www.exploit-db.com/exploits/44324WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan