What is CVE-2018-10237?

CVE-2018-10237 is a medium-severity insecure deserialization vulnerability in com.google.guava:guava-jdk5 (maven), affecting versions <= 17.0. It is fixed in 24.1.1-android. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2018-10237?

CVE-2018-10237 has a CVSS score of 5.9 (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-2018-10237?

com.google.guava:guava-jdk5 (maven) versions = 11.0, < 24.1.1-android.

Is there a fix for CVE-2018-10237?

Yes. CVE-2018-10237 is fixed in 24.1.1-android. Upgrade to this version or later.

Is CVE-2018-10237 exploitable, and should I be worried?

Whether CVE-2018-10237 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-2018-10237 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.

CVE-2018-10237 in com.google.guava:guava-jdk5

Q: How severe is CVE-2018-10237?

CVE-2018-10237 has a CVSS score of 5.9 (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-2018-10237?

com.google.guava:guava-jdk5 (maven) versions = 11.0, < 24.1.1-android.

Q: Is there a fix for CVE-2018-10237?

Yes. CVE-2018-10237 is fixed in 24.1.1-android. Upgrade to this version or later.

Q: Is CVE-2018-10237 exploitable, and should I be worried?

Whether CVE-2018-10237 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-2018-10237 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-2018-10237?

Upgrade com.google.guava:guava to 24.1.1-android or later.

Summary

Denial of Service in Google Guava

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.

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2018-10237 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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 (24.1.1-android); upgrading removes the vulnerable code path.

Affected versions

com.google.guava:guava-jdk5 (<= 17.0) com.googlecode.guava-osgi:guava-osgi (<= 11.0.1) de.mhus.ports:vaadin-shared-deps (<= 7.4.0) org.hudsonci.lib.guava:guava (<= 14.0.1-h-3) org.sonatype.sisu:sisu-guava (= 0.11.1) com.google.guava:guava (>= 11.0, < 24.1.1-android)

Security releases

com.google.guava:guava → 24.1.1-android (maven)

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

Upgrade com.google.guava:guava to 24.1.1-android or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-10237? CVE-2018-10237 is a medium-severity insecure deserialization vulnerability in com.google.guava:guava-jdk5 (maven), affecting versions <= 17.0. It is fixed in 24.1.1-android. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2018-10237? CVE-2018-10237 has a CVSS score of 5.9 (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-2018-10237?
- com.google.guava:guava-jdk5 (maven) (versions <= 17.0)
- com.googlecode.guava-osgi:guava-osgi (maven) (versions <= 11.0.1)
- de.mhus.ports:vaadin-shared-deps (maven) (versions <= 7.4.0)
- org.hudsonci.lib.guava:guava (maven) (versions <= 14.0.1-h-3)
- org.sonatype.sisu:sisu-guava (maven) (versions = 0.11.1)
- com.google.guava:guava (maven) (versions >= 11.0, < 24.1.1-android)
Is there a fix for CVE-2018-10237? Yes. CVE-2018-10237 is fixed in 24.1.1-android. Upgrade to this version or later.
Is CVE-2018-10237 exploitable, and should I be worried? Whether CVE-2018-10237 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-2018-10237 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-2018-10237? Upgrade com.google.guava:guava to 24.1.1-android or later.