CVE-2022-35915 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in @openzeppelin/contracts. O3 Security confirms whether CVE-2022-35915 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Unbounded gas consumption in @openzeppelin/contracts
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/contractsnpmopenzeppelin-soliditynpm@openzeppelin/contracts-upgradeablenpmDescription
OpenZeppelin Contracts is a library for secure smart contract development. The target contract of an EIP-165 supportsInterface query can cause unbounded gas consumption by returning a lot of data, while it is generally assumed that this operation has a bounded cost. The issue has been fixed in v4.7.2. Users are advised to upgrade. There are no known workarounds for this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @openzeppelin/contracts | ≥ 2.0.0&&< 4.7.2 | 4.7.2 |
| 📦npm | openzeppelin-solidity | ≥ 2.0.0 | No fix |
| 📦npm | @openzeppelin/contracts-upgradeable | ≥ 3.2.0&&< 4.7.2 | 4.7.2 |
| 📦npm | openzeppelin-eth | ≥ 2.0.0 | No fix |
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 CVE-2022-35915 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 CVE-2022-35915 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 CVE-2022-35915. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-35915 in your dependencies?
O3 detects CVE-2022-35915 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.