CVE-2019-9155: Openpgp Invalid Curve Attack Vulnerability

MODERATE
Advisory Identifier: GHSA-77jf-fjjf-xcww
CVSS 5.9
CWE-327
Published
Advisory Summary

CVE-2019-9155 is a MODERATE (CVSS 5.9) invalid curve attack vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Openpgp libraries in the npm ecosystem. The issue involves invalid curve attack in openpgp. Remediation is available by upgrading affected packages to version 4.3.0.

CVE-2019-9155 at a Glance

CVE Identifier CVE-2019-9155
GHSA Identifier GHSA-77jf-fjjf-xcww
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Openpgp
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2019-9155

To remediate this vulnerability, upgrade all affected Openpgp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openpgp fixed: 4.3.0
npm install openpgp@4.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openpgp

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2019-9155, inspect your project dependencies using npm:

npm ls openpgp

Analyze the terminal output to locate any version of Openpgp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.3.0), your application is affected.

Note: The npm ls openpgp command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Openpgp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Versions of `openpgp` prior to 4.3.0 are vulnerable to an Invalid Curve Attack. The package's implementation of ECDH fails to verify the validity of the communication partner's public key. The package calculates the resulting key secret based on an altered curve instead of the specified elliptic curve. Attackers may exfiltrate the victim's private key by choosing the altered curve. An attack requires the attacker being able to initiate message decryption and record the result. Furthermore the victim's key must offer an ECDH public key. ## Recommendation Upgrade to version 4.3.0 or later. If you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0

CVE-2019-9155 Affected Openpgp Versions

1 component(s)
Fixed Versions:
4.3.0
Product / Package Ecosystem Affected Versions Fixed Version
openpgp
npm
< 4.3.0
4.3.0

References

Frequently Asked Questions

What is CVE-2019-9155?
CVE-2019-9155 is a security vulnerability in Openpgp involving Invalid Curve Attack in openpgp under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Openpgp versions are affected?
Affected versions include releases prior to 4.3.0 across affected packages: openpgp.
What version fixes CVE-2019-9155?
Upgrading to 4.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openpgp affected?
Yes, openpgp is affected in releases prior to 4.3.0. Upgrade your dependency to 4.3.0 or later.
What is the CVSS score of CVE-2019-9155?
CVE-2019-9155 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2019-9155?
CVE-2019-9155 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check npm dependencies for CVE-2019-9155?
Run the dependency tree command: 'npm ls openpgp'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-77jf-fjjf-xcww",
  "modified" : "2021-07-27T21:15:18Z",
  "published" : "2019-08-23T21:42:22Z",
  "aliases" : [ "CVE-2019-9155" ],
  "summary" : "Invalid Curve Attack in openpgp",
  "details" : "Versions of `openpgp` prior to 4.3.0 are vulnerable to an Invalid Curve Attack. The package's implementation of ECDH fails to verify the validity of the communication partner's public key. The package calculates the resulting key secret based on an altered curve instead of the specified elliptic curve. Attackers may exfiltrate the victim's private key by choosing the altered curve. An attack requires the attacker being able to initiate message decryption and record the result. Furthermore the victim's key must offer an ECDH public key.\n\n\n## Recommendation\n\nUpgrade to version 4.3.0 or later.\nIf you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openpgp"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-9155"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openpgpjs/openpgpjs/pull/853"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openpgpjs/openpgpjs/pull/853/commits/7ba4f8c655e7fd7706e8d7334e44b40fdf56c43e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openpgpjs/openpgpjs/releases/tag/v4.3.0"
  }, {
    "type" : "WEB",
    "url" : "https://sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js"
  }, {
    "type" : "WEB",
    "url" : "https://snyk.io/vuln/SNYK-JS-OPENPGP-460225"
  }, {
    "type" : "WEB",
    "url" : "https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html#download=1"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1159"
  }, {
    "type" : "WEB",
    "url" : "http://packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attack.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2019-08-23T21:39:35Z",
    "nvd_published_at" : "2019-08-22T16:15:00Z"
  }
}