Rhino has high CPU usage and potential DoS when passing specific numbers to `toFixed()` functionGHSA-3w8q-xq97-5j7x
Fix: mozilla/rhino@2bcf4c4GHSA-3w8q-xq97-5j7x is a Uncontrolled Resource Consumption vulnerability in org.mozilla:rhino. A fix is available for org.mozilla:rhino — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3w8q-xq97-5j7x.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.mozilla:rhino☕org.mozilla:rhino☕org.mozilla:rhinoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Rhino is an open-source implementation of JavaScript written entirely in Java. Prior to 1.8.1, 1.7.15.1, and 1.7.14.1, 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. This vulnerability is fixed in 1.8.1, 1.7.15.1, and 1.7.14.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.mozilla:rhino | all versions | 1.7.14.1org.mozilla:rhino:1.7.14.1 |
| ☕Maven | org.mozilla:rhino | ≥ 1.7.15&&< 1.7.15.1 | 1.7.15.1org.mozilla:rhino:1.7.15.1 |
| ☕Maven | org.mozilla:rhino | ≥ 1.8.0&&< 1.8.1 | 1.8.1org.mozilla:rhino:1.8.1 |
Affected Products
rhinomozillaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mozilla:rhino, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mozilla:rhino to 1.7.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3w8q-xq97-5j7x is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-3w8q-xq97-5j7x in your dependencies?
Find it across Maven, including transitive dependencies.