CVE-2022-25324: Bignum Uncaught Exception Vulnerability

HIGH
Advisory Identifier: GHSA-6429-3g3w-6mw5
CVSS 7.5
CWE-248
Published
Advisory Summary

CVE-2022-25324 is a HIGH (CVSS 7.5) uncaught exception vulnerability (CWE-248: Uncaught Exception) affecting Bignum libraries in the npm ecosystem. The issue involves uncaught exception in bignum. Remediation is available in the latest vendor maintenance releases.

CVE-2022-25324 at a Glance

CVE Identifier CVE-2022-25324
GHSA Identifier GHSA-6429-3g3w-6mw5
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-248: Uncaught Exception
Affected Product Bignum
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

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

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

How to Fix CVE-2022-25324

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

bignum fixed: Latest secure release
npm install bignum@Latest secure release
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 bignum

How to Check if You Are Affected

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

npm ls bignum

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

Note: The npm ls bignum 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-248: Uncaught Exception, where an exception is thrown from a function, but it is not caught. In Bignum, 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

All versions of the npm package bignum are vulnerable to Denial of Service (DoS) due to a type-check exception in V8. When verifying the type of the second argument to the .powm function, V8 will crash regardless of Node try/catch blocks.

CVE-2022-25324 Affected Bignum Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
bignum
npm
≤ 0.13.1

References

Frequently Asked Questions

What is CVE-2022-25324?
CVE-2022-25324 is a security vulnerability in Bignum involving Uncaught Exception in bignum under CWE-248: Uncaught Exception.
Which Bignum versions are affected?
Affected versions include releases prior to current release patches across affected packages: bignum.
What version fixes CVE-2022-25324?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is bignum affected?
Yes, bignum is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2022-25324?
CVE-2022-25324 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2022-25324?
CVE-2022-25324 is classified under CWE-248: Uncaught Exception (An exception is thrown from a function, but it is not caught.).
How can I check npm dependencies for CVE-2022-25324?
Run the dependency tree command: 'npm ls bignum'. 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-6429-3g3w-6mw5",
  "modified" : "2022-05-24T20:58:02Z",
  "published" : "2022-05-07T00:00:31Z",
  "aliases" : [ "CVE-2022-25324" ],
  "summary" : "Uncaught Exception in bignum",
  "details" : "All versions of the npm package bignum are vulnerable to Denial of Service (DoS) due to a type-check exception in V8. When verifying the type of the second argument to the .powm function, V8 will crash regardless of Node try/catch blocks.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "bignum"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.13.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-25324"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/justmoon/node-bignum"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/justmoon/node-bignum/blob/ef2e02533e598d6df8421000033c4753cde89ee2/index.js#L111"
  }, {
    "type" : "WEB",
    "url" : "https://snyk.io/vuln/SNYK-JS-BIGNUM-2388581"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-248" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-05-24T20:58:02Z",
    "nvd_published_at" : "2022-05-06T20:15:00Z"
  }
}