`chainId` may be outdated if user changes chains as part of connection in @web3-react
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
@web3-react is a framework for building Ethereum Apps . In affected versions the `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 issue has been addressed in PR #749 and is available in updated npm artifacts. There are no known workarounds for this issue. Users are advised to upgrade.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Uniswap web3-react
Version range not reported
- @web3-react/coinbase-walletnpm
From 6.0.0 · fixed in 8.0.35-beta.0
- @web3-react/eip1193npm
From 6.0.0 · fixed in 8.0.27-beta
- @web3-react/metamasknpm
From 6.0.0 · fixed in 8.0.30-beta.0
- @web3-react/walletconnectnpm
From 6.0.0 · fixed in 8.0.37-beta.0