Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-8m45-2rjm-j347

HIGH

Handling untrusted input can result in a crash, leading to loss of availability / denial of service

Also known asCVE-2024-30253
Published
Apr 17, 2024
Updated
Apr 17, 2024
Affected
92 pkgs
Patched
92 / 92
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk44th percentile+0.45%
0.00%0.36%0.73%1.09%0.1%0.6%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

92 pkgs affected
📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js📦@solana/web3.js+84 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Using particular inputs with @solana/web3.js will result in memory exhaustion (OOM).

If you have a server, client, mobile, or desktop product that accepts untrusted input for use with @solana/web3.js, your application/service may crash, resulting in a loss of availability.

Affected Packages

92 total 92 fixed
EcosystemPackageVulnerable rangeFix
📦npm@solana/web3.js1.91.0&&< 1.91.31.91.3
📦npm@solana/web3.js1.90&&< 1.90.21.90.2
📦npm@solana/web3.js1.89&&< 1.89.21.89.2
📦npm@solana/web3.js1.88.0&&< 1.88.11.88.1
📦npm@solana/web3.js1.87.0&&< 1.87.71.87.7
📦npm@solana/web3.js1.86.0&&< 1.86.11.86.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @solana/web3.js. 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.

  2. Fix

    Update @solana/web3.js to 1.91.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m45-2rjm-j347 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8m45-2rjm-j347 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-8m45-2rjm-j347. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Using particular inputs with `@solana/web3.js` will result in memory exhaustion (OOM). If you have a server, client, mobile, or desktop product that accepts untrusted input for use with `@solana/web3.js`, your application/service may crash, resulting in a loss of availability.
O3 Security · Impact-Aware SCA

Is GHSA-8m45-2rjm-j347 in your dependencies?

O3 detects GHSA-8m45-2rjm-j347 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-8m45-2rjm-j347: @solana/web3.js (High 7.5) | O3 Security