Blast Radius
com.google.guava:guava☕com.google.guava:guava-jdk5☕com.googlecode.guava-osgi:guava-osgi☕de.mhus.ports:vaadin-shared-deps☕org.hudsonci.lib.guava:guava☕org.sonatype.sisu:sisu-guavaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.google.guava:guava | ≥ 11.0&&< 24.1.1-android | 24.1.1-android |
| ☕Maven | com.google.guava:guava-jdk5 | all versions | No fix |
| ☕Maven | com.googlecode.guava-osgi:guava-osgi | all versions | No fix |
| ☕Maven | de.mhus.ports:vaadin-shared-deps | all versions | No fix |
| ☕Maven | org.hudsonci.lib.guava:guava | all versions | No fix |
| ☕Maven | org.sonatype.sisu:sisu-guava | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.guava:guava. 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 com.google.guava:guava to 24.1.1-android or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10237 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-2018-10237 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-2018-10237. 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-2018-10237 in your dependencies?
O3 detects CVE-2018-10237 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.