Skip to content
Fencer Intel
high 7.5

CVE-2018-0114 in the critical feed json

Cisco node-jose improper validation of JWT signature

published 8y ago modified 4mo ago also GHSA-jfxm-w8g2-4rcv , EUVD-2022-4353

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
42.7%
EPSS 42.7% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • npm node-jose 0.11.0
  • cisco node-jose 0.11.0

Is CVE-2018-0114 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 Fencer

Timeline

  1. Published
  2. First public exploit (EDB-44324)

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

42.65% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-44324 Cisco node-jos < 0.11.0 - Re-sign Tokens webapps, 2018-03-20
  • github.com https://github.com/zi0Black/POC-CVE-2018-0114 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm node-jose
<0.11.0
0.11.0

Affected products

  • n/a Node-jose Library

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

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.