# CVE-2017-16007: Cisco node-jose invalid curve attack in ECDH-ES

Source: https://junglewise.ai/threats/cve-2017-16007-cisco-node-jose-invalid-curve-attack-in-ecdh-es  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2018-07-20. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2017-16007 · Severity: low · CVSS 3 · Published 2018-07-20

node-jose is a JavaScript library used for JSON Web Encryption (JWE) operations in web applications and APIs. An invalid curve attack in the ECDH-ES key agreement algorithm allows an attacker to recover the private secret key used to decrypt sensitive data, potentially exposing encrypted communications and authentication credentials.

Technologies: [node-jose (npm)](https://junglewise.ai/threats/technologies/node-jose). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2017-16007 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2017-16007 being exploited in the wild.

**How severe is CVE-2017-16007?** Low severity, with a CVSS score of 3, published 20 July 2018.

**Which products and versions are affected?** node-jose (npm) SEMVER:introduced=0,fixed=0.9.3.

**Is there a fix for CVE-2017-16007?** Yes. node-jose (npm): upgrade to 0.9.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2017-16007 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2017-16007?** Check whether you run node-jose (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- node-jose (npm): upgrade to 0.9.3 or later

  ```sh
  npm install node-jose@0.9.3
  ```


## Technical details

The vulnerability is a cryptographic attack in the ECDH-ES (Elliptic Curve Diffie-Hellman Ephemeral Static) key agreement implementation. The library failed to validate that received elliptic curve public keys were on the configured curve, allowing an attacker to supply a specially crafted public key from an invalid curve and recover the private key through mathematical analysis. This affects all versions prior to 0.9.3, which introduced proper public key validation. The attack is network-accessible and requires no authentication or user interaction, but involves non-trivial cryptographic manipulation (AC:H indicates high complexity).

## Affected products

- Cisco node-jose before 0.9.3

## Identifiers

- CVE-2017-16007
- GHSA-rvj9-8cvx-3vq9

## Timeline

- 2017-03: disclosed: Vulnerability details published by researcher
- 2017-02-15: patched: Fix merged validating EC public key is on configured curve
- 2018-07-20: advisory

## References

- [https://github.com/cisco/node-jose/pull/88](https://github.com/cisco/node-jose/pull/88)

## Related threats

- [Cisco node-jose ECC infinite loop denial of service](https://junglewise.ai/threats/cve-2023-25653-cisco-node-jose-ecc-infinite-loop-denial-of-service)
- [Cisco node-jose improper JWT signature validation](https://junglewise.ai/threats/cve-2018-0114-cisco-node-jose-improper-jwt-signature-validation)