LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10237: Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to cond...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service issue in older Google Guava library versions. If a server accepts attacker-controlled serialized data and uses affected Guava classes, a remote attacker may force excessive memory allocation and disrupt service availability.

Executive priority

Prioritize systems where service availability matters and external users can submit serialized data. This is not evidenced as actively exploited in the bundle, but vulnerable internet-facing deserialization paths could create operational disruption.

Technical view

Guava 11.0 through 24.x before 24.1.1 can eagerly allocate memory during deserialization. The cited CVE identifies AtomicDoubleArray with Java serialization and CompoundOrdering with GWT serialization as affected paths when attacker-provided data is deserialized without reasonable size checks.

Likely exposure

Exposure is most likely in Java services or products that bundle vulnerable Guava versions and deserialize client-controlled Java or GWT serialized data. The source bundle does not identify specific non-Red Hat affected products beyond Guava version ranges and referenced downstream discussions.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation depends on reaching an application path that deserializes attacker-provided data using the affected Guava classes.

Researcher notes

Focus triage on reachability, not only package presence. A vulnerable Guava jar is most meaningful where attacker-controlled serialized input reaches AtomicDoubleArray Java serialization or CompoundOrdering GWT serialization behavior.

Mitigation direction

  • Upgrade Guava to 24.1.1 or later where directly managed.
  • Apply vendor-supported fixed packages for Red Hat-distributed products.
  • Inventory transitive dependencies that may bundle vulnerable Guava versions.
  • Avoid deserializing untrusted Java or GWT serialized data where possible.
  • Check vendor advisories for product-specific fixed versions and backports.

Validation and detection

  • Search dependency manifests and SBOMs for Guava versions before 24.1.1.
  • Confirm whether exposed services deserialize client-controlled Java or GWT serialized data.
  • Check packaged products against relevant Red Hat advisories.
  • Verify runtime artifacts do not contain older shaded or bundled Guava copies.
  • Document any compensating controls for unavoidable legacy deployments.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-10237 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
40Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.