Approved changes feed: RSS · Atom

cpe:2.3:a:cisco:node-jose:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorCisco (e1b3baff-aaf9-56a6-a68a-41e28ce616a5)
ProductNode Jose (44e6b598-384b-5ac9-81d6-d0a10a696a74)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/cisco/node-jose purl2cpe 2026-06-01 10:12:57.847603
pkg:maven/org.webjars.npm/node-jose purl2cpe 2026-06-01 10:12:57.847607
pkg:npm/node-jose purl2cpe 2026-06-01 10:12:57.847610

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-25653 vulnerable 2026-06-08 05:56:09.605348 Improper calculations in ECC implementation can trigger a Denial-of-Service (DoS)
HIGH (7.5)
node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to version 2.2.0, when using the non-default "fallback" crypto back-end, ECC operations in `node-jose` can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation. For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input. The issue has been patched in version 2.2.0. Since this issue is only present in the "fallback" crypto implementation, it can be avoided by ensuring that either WebCrypto or the Node `crypto` module is available in the JS environment where `node-jose` is being run.
Published: 2023-02-16T18:15:27.085Z
Updated: 2025-03-10T21:10:13.531Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-0114 vulnerable 2026-06-08 05:10:21.113355 Details available
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.
Published: 2018-01-04T06:00:00.000Z
Updated: 2024-12-02T20:58:29.226Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.