Skip to content

Denial of Service in Google Guava

Moderate severity GitHub Reviewed Published Jun 15, 2020 to the GitHub Advisory Database • Updated Nov 9, 2023

Package

maven com.google.guava:guava (Maven)

Affected versions

>= 11.0, < 24.1.1-android

Patched versions

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

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.

References

Published by the National Vulnerability Database Apr 26, 2018
Reviewed Jun 11, 2020
Published to the GitHub Advisory Database Jun 15, 2020
Last updated Nov 9, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

1.263%
(86th percentile)

Weaknesses

CVE ID

CVE-2018-10237

GHSA ID

GHSA-mvr2-9pj6-7w5j

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.