GHSA-3W8Q-XQ97-5J7X

Vulnerability from github – Published: 2025-12-03 16:57 – Updated: 2025-12-04 16:23
VLAI
Summary
Rhino has high CPU usage and potential DoS when passing specific numbers to `toFixed()` function
Details

When an application passed an attacker controlled float poing number into the toFixed() function, it might lead to high CPU consumption and a potential Denial of Service.

Small numbers go through this call stack: NativeNumber.numTo > DToA.JS_dtostr > DToA.JS_dtoa > DToA.pow5mult where pow5mult attempts to raise 5 to a ridiculous power.

Example code: (4.47118444E-314).toFixed(2)

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.mozilla:rhino"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.7.14.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.mozilla:rhino"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.7.15"
            },
            {
              "fixed": "1.7.15.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.mozilla:rhino"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.8.0"
            },
            {
              "fixed": "1.8.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.8.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-66453"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-03T16:57:50Z",
    "nvd_published_at": "2025-12-03T20:16:26Z",
    "severity": "LOW"
  },
  "details": "When an application passed an attacker controlled float poing number into the `toFixed()` function, it might lead to high CPU consumption and a potential Denial of Service.\n\nSmall numbers go through this call stack: `NativeNumber.numTo \u003e DToA.JS_dtostr \u003e DToA.JS_dtoa \u003e DToA.pow5mult`\nwhere `pow5mult` attempts to raise `5` to a ridiculous power.\n\nExample code: `(4.47118444E-314).toFixed(2)`",
  "id": "GHSA-3w8q-xq97-5j7x",
  "modified": "2025-12-04T16:23:15Z",
  "published": "2025-12-03T16:57:50Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/mozilla/rhino/security/advisories/GHSA-3w8q-xq97-5j7x"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66453"
    },
    {
      "type": "WEB",
      "url": "https://github.com/mozilla/rhino/commit/2bcf4c43deace35f1f57d86377c6767b0608986e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mozilla/rhino"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Rhino has high CPU usage and potential DoS when passing specific numbers to `toFixed()` function"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…