What is CVE-2023-30543?

CVE-2023-30543 is a medium-severity race condition vulnerability in @web3-react/coinbase-wallet (npm), affecting versions >= 6.0.0, < 8.0.35-beta.0. It is fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is CVE-2023-30543?

CVE-2023-30543 has a CVSS score of 5.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2023-30543?

@web3-react/coinbase-wallet (npm) versions >= 6.0.0, = 6.0.0, = 6.0.0, = 6.0.0, < 8.0.37-beta.0.

Is there a fix for CVE-2023-30543?

Yes. CVE-2023-30543 is fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0. Upgrade to this version or later.

Is CVE-2023-30543 exploitable, and should I be worried?

Whether CVE-2023-30543 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-30543 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-30543?

Upgrade: @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, @web3-react/eip1193 to 8.0.27-beta or later, @web3-react/metamask to 8.0.30-beta.0 or later, @web3-react/walletconnect to 8.0.37-beta.0 or later.

CVE-2023-30543 in @web3-react/coinbase-wallet

Q: How severe is CVE-2023-30543?

CVE-2023-30543 has a CVSS score of 5.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2023-30543?

@web3-react/coinbase-wallet (npm) versions >= 6.0.0, = 6.0.0, = 6.0.0, = 6.0.0, < 8.0.37-beta.0.

Q: Is there a fix for CVE-2023-30543?

Yes. CVE-2023-30543 is fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0. Upgrade to this version or later.

Q: Is CVE-2023-30543 exploitable, and should I be worried?

Whether CVE-2023-30543 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-30543 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-30543?

Upgrade: @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, @web3-react/eip1193 to 8.0.27-beta or later, @web3-react/metamask to 8.0.30-beta.0 or later, @web3-react/walletconnect to 8.0.37-beta.0 or later.

Summary

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

Workarounds

N/A

References

N/A

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.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2023-30543 has a CVSS score of 5.2 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0); upgrading removes the vulnerable code path.

Affected versions

@web3-react/coinbase-wallet (>= 6.0.0, < 8.0.35-beta.0) @web3-react/eip1193 (>= 6.0.0, < 8.0.27-beta.0) @web3-react/metamask (>= 6.0.0, < 8.0.30-beta.0) @web3-react/walletconnect (>= 6.0.0, < 8.0.37-beta.0)

Security releases

@web3-react/coinbase-wallet → 8.0.35-beta.0 (npm) @web3-react/eip1193 → 8.0.27-beta (npm) @web3-react/metamask → 8.0.30-beta.0 (npm) @web3-react/walletconnect → 8.0.37-beta.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2023-30543? CVE-2023-30543 is a medium-severity race condition vulnerability in @web3-react/coinbase-wallet (npm), affecting versions >= 6.0.0, < 8.0.35-beta.0. It is fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is CVE-2023-30543? CVE-2023-30543 has a CVSS score of 5.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2023-30543?
- @web3-react/coinbase-wallet (npm) (versions >= 6.0.0, < 8.0.35-beta.0)
- @web3-react/eip1193 (npm) (versions >= 6.0.0, < 8.0.27-beta.0)
- @web3-react/metamask (npm) (versions >= 6.0.0, < 8.0.30-beta.0)
- @web3-react/walletconnect (npm) (versions >= 6.0.0, < 8.0.37-beta.0)
Is there a fix for CVE-2023-30543? Yes. CVE-2023-30543 is fixed in 8.0.35-beta.0, 8.0.27-beta, 8.0.30-beta.0, 8.0.37-beta.0. Upgrade to this version or later.
Is CVE-2023-30543 exploitable, and should I be worried? Whether CVE-2023-30543 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-30543 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-30543?
- Upgrade @web3-react/coinbase-wallet to 8.0.35-beta.0 or later
- Upgrade @web3-react/eip1193 to 8.0.27-beta or later
- Upgrade @web3-react/metamask to 8.0.30-beta.0 or later
- Upgrade @web3-react/walletconnect to 8.0.37-beta.0 or later