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

GHSA-8pf3-6fgr-3g3g

MEDIUM

`chainId` may be outdated if user changes chains as part of connection in @web3-react

Also known asCVE-2023-30543
Published
Apr 18, 2023
Updated
Nov 8, 2023
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk29th percentile+0.23%
0.00%0.29%0.59%0.88%0.0%0.4%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

4 pkgs affected

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

@web3-react/coinbase-walletnpm
6Kdownloads / week
@web3-react/eip1193npm
6Kdownloads / week
@web3-react/metamasknpm
9Kdownloads / week

Description

Impact

chainId may be outdated if the user changes chains as part of the connection flow. This means that the value of chainId returned by useWeb3React() may be incorrect. In an application, this means that any data derived from chainId could be incorrect.

For example, if a swapping application derives a wrapped token contract address from the chainId and a user has changed chains as part of their connection flow the application could cause the user to send funds to the incorrect address when wrapping. This is a common approach when using other foundational libraries like ethers, and most users of v8 will want to upgrade past the affected versions.

Patches

Patched in https://github.com/Uniswap/web3-react/pull/749. Users of [email protected] should upgrade to at least:

  • @web3-react/coinbase-wallet@^8.0.35-beta.0
  • @web3-react/eip1193@^8.0.27-beta.0
  • @web3-react/metamask@^8.0.30-beta.0
  • @web3-react/walletconnect@^8.0.37-beta.0

Workarounds

N/A

References

N/A

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npm@web3-react/coinbase-wallet6.0.0&&< 8.0.35-beta.08.0.35-beta.0
📦npm@web3-react/eip11936.0.0&&< 8.0.27-beta8.0.27-beta
📦npm@web3-react/metamask6.0.0&&< 8.0.30-beta.08.0.30-beta.0
📦npm@web3-react/walletconnect6.0.0&&< 8.0.37-beta.08.0.37-beta.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @web3-react/coinbase-wallet. 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 @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8pf3-6fgr-3g3g 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-8pf3-6fgr-3g3g 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-8pf3-6fgr-3g3g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact `chainId` may be outdated if the user changes chains as part of the connection flow. This means that the value of `chainId` returned by `useWeb3React()` may be incorrect. In an application, this means that any data derived from `chainId` could be incorrect. For example, if a swapping application derives a wrapped token contract address from the `chainId` *and* a user has changed chains as part of their connection flow the application could cause the user to send funds to the incorrect address when wrapping. This is a common approach when using other foundational libraries like [`et
O3 Security · Impact-Aware SCA

Is GHSA-8pf3-6fgr-3g3g in your dependencies?

O3 detects GHSA-8pf3-6fgr-3g3g across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.