← Vulnerability feed

Vulnerability record · CVE-2018-0114 · published 4 January 2018

CVE-2018-0114: Cisco node-jose improper verification of cryptographic signature vulnerability

Cisco · Node Jose

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.

7.5 CVSS 3.1 High EPSS 43% · top 1.3% CWE-347 · Improper verification of cryptographic signature
7.5CVSS 3.1 base score, v2 5.0
43%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
10References, 2 tagged exploit
17 Jun 2026Last modified by NVD

Description

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.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

LinkTags
http://www.securityfocus.com/bid/102445 Third Party AdvisoryVDB Entry
https://github.com/cisco/node-jose/blob/master/CHANGELOG.md Release NotesThird Party Advisory
https://github.com/zi0Black/POC-CVE-2018-0114 ExploitThird Party Advisory
https://tools.cisco.com/security/center/viewAlert.x?alertId=56326 PatchVendor Advisory
https://www.exploit-db.com/exploits/44324/ Third Party AdvisoryVDB Entry
http://www.securityfocus.com/bid/102445 Third Party AdvisoryVDB Entry
https://github.com/cisco/node-jose/blob/master/CHANGELOG.md Release NotesThird Party Advisory
https://github.com/zi0Black/POC-CVE-2018-0114 ExploitThird Party Advisory
https://tools.cisco.com/security/center/viewAlert.x?alertId=56326 PatchVendor Advisory
https://www.exploit-db.com/exploits/44324/ Third Party AdvisoryVDB Entry

Track CVE-2018-0114 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

7.5CVE-2023-25653Cisco node-jose vulnerabilitynode-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to versio…EPSS 0.55%5.9CVE-2017-16007Cisco node-jose information exposure vulnerabilitynode-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for current web browsers and node.js-based servers. node-jo…EPSS 0.93%10.0CVE-2026-5430Wso2 api control plane improper verification of cryptographic signature vulnerabilityThe JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker t…KEVEPSS 0.59%9.5CVE-2026-48558SimpleHelp OIDC authentication bypass via unverified token signatureSimpleHelp 5.5.15 and earlier and 6.0 pre-release versions accept OIDC identity tokens without verifying their cryptographic signature. When OIDC is …KEVEPSS 5.7%analysed9.8CVE-2025-59718Fortinet FortiOS/FortiProxy SAML signature check bypass in FortiCloud SSOFortiOS, FortiProxy and FortiSwitchManager fail to properly verify the cryptographic signature of SAML responses used for FortiCloud SSO login. An un…KEVEPSS 68%analysed4.6CVE-2025-47827IGEL OS Secure Boot bypass via improper signature verificationIGEL OS before version 11 fails to properly verify a cryptographic signature in the igel-flash-driver module, allowing Secure Boot to be bypassed. A …KEVEPSS 4.9%analysed10.0CVE-2020-2021PAN-OS SAML signature verification bypass allows authentication bypassPAN-OS fails to properly verify SAML signatures when SAML authentication is enabled and the 'Validate Identity Provider Certificate' option is unchec…KEVEPSS 4.4%analysed5.5CVE-2013-3900Windows WinVerifyTrust Authenticode signature verification RCECVE-2013-3900 is a remote code execution flaw in how the Windows WinVerifyTrust function verifies Authenticode signatures on portable executable file…KEVEPSS 45%analysed

Source: NIST National Vulnerability Database (record CVE-2018-0114), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.