Uncontrolled Resource Consumption in json-bigintGHSA-wgfq-7857-4jcc
HIGHGHSA-wgfq-7857-4jcc is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in json-bigint. 1 public exploit reference exists, so weaponization risk is real. A fix is available for json-bigint — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-wgfq-7857-4jcc by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
json-bigintnpmDescription
Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | json-bigint | all versions | 1.0.0npm install json-bigint@1.0.0 |
Affected Products
json-bigintjson-bigint_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json-bigint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update json-bigint to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wgfq-7857-4jcc 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In Red Hat Openshift Container Storage 4 the noobaa-core container includes the affected version of json-bigint as a dependency of googleapis, however the json-bigint library is not being used and hence this issue has been rated as having a security impact of Low.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Storage 4.6.0 on RHEL-8 | ocs4/mcg-core-rhel8:5.6.0-38.31e0c3c7b.5.6 | RHSA-2020:5605 |
Frequently Asked Questions
Is GHSA-wgfq-7857-4jcc in your dependencies?
Find it across npm, including transitive dependencies.