GHSA-9j3m-g383-29qr is a medium-severity (CVSS 5.3) CWE-669 vulnerability in @openzeppelin/contracts. O3 Security confirms whether GHSA-9j3m-g383-29qr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenZeppelin Contracts's Cross chain utilities for Arbitrum L2 see EOA calls as cross chain calls
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@openzeppelin/contractsnpm@openzeppelin/contracts-upgradeablenpmDescription
Impact
Contracts using the cross chain utilies for Arbitrum L2, CrossChainEnabledArbitrumL2 or LibArbitrumL2, will classify direct interactions of externally owned accounts (EOAs) as cross chain calls, even though they are not started on L1. This is assessed as low severity because any action taken by an EOA on the contract could also be taken by the EOA through the bridge if the issue was not present.
Patches
This issue has been patched in v4.7.2.
References
https://github.com/OpenZeppelin/openzeppelin-contracts/pull/3578
For more information
If you have any questions or comments about this advisory, or need assistance deploying a fix, email us at [email protected].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @openzeppelin/contracts | ≥ 4.6.0&&< 4.7.2 | 4.7.2 |
| 📦npm | @openzeppelin/contracts-upgradeable | ≥ 4.6.0&&< 4.7.2 | 4.7.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openzeppelin/contracts. 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.
Fix
Update @openzeppelin/contracts to 4.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9j3m-g383-29qr is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-9j3m-g383-29qr 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-9j3m-g383-29qr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9j3m-g383-29qr in your dependencies?
O3 detects GHSA-9j3m-g383-29qr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.