How severe is GHSA-7cgc-fjv4-52x6?

No CVSS score has been assigned to GHSA-7cgc-fjv4-52x6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7cgc-fjv4-52x6?

GHSA-7cgc-fjv4-52x6 affects the following packages: bignum (npm). Ecosystems affected: npm.

How do I fix GHSA-7cgc-fjv4-52x6?

Update bignum to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cgc-fjv4-52x6 is resolved across your whole dependency graph.

How do I detect GHSA-7cgc-fjv4-52x6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bignum. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7cgc-fjv4-52x6 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.

How does O3 Security protect against GHSA-7cgc-fjv4-52x6?

O3 pinpoints whether GHSA-7cgc-fjv4-52x6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7cgc-fjv4-52x6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7cgc-fjv4-52x6 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-7cgc-fjv4-52x6 published, and has it been updated?

GHSA-7cgc-fjv4-52x6 was published on May 24, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-7cgc-fjv4-52x6

GHSA-7cgc-fjv4-52x6 is a security vulnerability in bignum. O3 Security confirms whether GHSA-7cgc-fjv4-52x6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malware in pre-build binaries of bignum

Published

May 24, 2023

Updated

May 24, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

bignumnpm

4Kdownloads / week

Description

Impact

bignum releases from v0.12.2 to v0.13.0 (inclusive) used node-pre-gyp to optionally download pre-built binary versions of the addon. These binaries were published on a now-expired S3 bucket which has since been claimed by a malicious third party which is now serving binaries containing malware that exfiltrates data from the user's computer.

Patches

v0.13.1 does not use node-pre-gyp and does not have support for downloading pre-built binaries in any form, avoiding the risk of malicious downloads.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bignum`	≥ 0.12.2&&< 0.13.1	0.13.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bignum. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update bignum to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cgc-fjv4-52x6 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.
How O3 protects you
O3 pinpoints whether GHSA-7cgc-fjv4-52x6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7cgc-fjv4-52x6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact bignum releases from v0.12.2 to v0.13.0 (inclusive) used node-pre-gyp to optionally download pre-built binary versions of the addon. These binaries were published on a now-expired S3 bucket which has since been claimed by a malicious third party which is now serving binaries containing malware that exfiltrates data from the user's computer. ### Patches v0.13.1 does not use node-pre-gyp and does not have support for downloading pre-built binaries in any form, avoiding the risk of malicious downloads.

O3 Security · Impact-Aware SCA

Is GHSA-7cgc-fjv4-52x6 in your dependencies?

O3 detects GHSA-7cgc-fjv4-52x6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works