How severe is GHSA-9r3m-mhfm-39cm?

No CVSS score has been assigned to GHSA-9r3m-mhfm-39cm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9r3m-mhfm-39cm?

GHSA-9r3m-mhfm-39cm affects the following packages: bigint-money (npm). Ecosystems affected: npm.

How do I fix GHSA-9r3m-mhfm-39cm?

Update bigint-money to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9r3m-mhfm-39cm is resolved across your whole dependency graph.

How do I detect GHSA-9r3m-mhfm-39cm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bigint-money, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9r3m-mhfm-39cm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-9r3m-mhfm-39cm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9r3m-mhfm-39cm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9r3m-mhfm-39cm published, and has it been updated?

GHSA-9r3m-mhfm-39cm was published on September 11, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Incorrect Calculation in bigint-moneyGHSA-9r3m-mhfm-39cm

GHSA-9r3m-mhfm-39cm is a security vulnerability in bigint-money. A fix is available for bigint-money — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

bigint-moneynpm

2Kdownloads / week

Description

Versions of bigint-money prior to 0.6.2 are vulnerable to an Incorrect Calculation. The package incorrectly rounded certain numbers, which could have drastic consequences due to its usage in financial systems.

Recommendation

Upgrade to version 0.6.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bigint-money`	all versions	0.6.2`npm install bigint-money@0.6.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bigint-money, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bigint-money to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9r3m-mhfm-39cm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `bigint-money` prior to 0.6.2 are vulnerable to an Incorrect Calculation. The package incorrectly rounded certain numbers, which could have drastic consequences due to its usage in financial systems. ## Recommendation Upgrade to version 0.6.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9r3m-mhfm-39cm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works