title: `chainId` may be outdated if user changes chains as part of connection in @web3-react
description: @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.
problem types: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
affected:
{
vendor: Uniswap
product: web3-react
versions:
version: @web3-react/coinbase-wallet: >= 6, < 8.0.35-beta.0, status: affected
version: @web3-react/eip1193: >= 6, < 8.0.27-beta.0, status: affected
version: @web3-react/metamask: >= 6, < 8.0.30-beta.0, status: affected
version: @web3-react/walletconnect: >= 6, < 8.0.37-beta.0, status: affected
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 5.2
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: HIGH
privilegesRequired: HIGH
scope: UNCHANGED
userInteraction: REQUIRED
vectorString: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L
version: 3.1
]