Uniswap Web3-React WalletConnect 8.0.24 Beta 0 for Node.js
Approved changes feed: RSS · Atom
cpe:2.3:a:uniswap:web3-react_walletconnect:8.0.24:beta0:*:*:*:node.js:*:*
part: a version: 8.0.24 update: beta0
| Vendor | Uniswap (07874f5b-33d3-5ec1-bd85-c23dcd67c08a) |
|---|---|
| Product | Web3 React Walletconnect (f6fca6d2-386b-54db-8a1f-2a7029902af6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/uniswap/web3-react |
purl2cpe | 2026-06-01 10:18:04.102211 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-30543 |
vulnerable | 2026-06-08 06:04:39.836423 |
`chainId` may be outdated if user changes chains as part of connection in @web3-react
MEDIUM (5.2)
@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.
Published: 2023-04-17T21:02:20.566Z
Updated: 2025-02-05T20:44:45.955Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.