CVE-2018-10237GHSA-MVR2-9PJ6-7W5J
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks aga
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 24.1.1-android
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- com.google.guava:guavaMaven
From 11.0 · fixed in 24.1.1-android
- com.google.guava:guava-jdk5Maven
through 17.0
- com.googlecode.guava-osgi:guava-osgiMaven
through 11.0.1
- de.mhus.ports:vaadin-shared-depsMaven
through 7.4.0
- org.hudsonci.lib.guava:guavaMaven
through 14.0.1-h-3
- org.sonatype.sisu:sisu-guavaMaven
0.11.1
References 25
access.redhat.com
securitytracker.com
lists.apache.org
- thread.html/cc48fe770c45a74dc3b37ed0817393e0c96701fc49bc431ed922f3cc@<hdfs-dev.hadoop.apache.org>
- thread.html/19fa48533bc7ea1accf6b12746a74ed888ae6e49a5cf81ae4f807495@<common-dev.hadoop.apache.org>
- thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@<commits.pulsar.apache.org>
- thread.html/3ddd79c801edd99c0978e83dbe2168ebd36fd42acfa5dac38fb03dd6@<issues.activemq.apache.org>
- thread.html/3d5dbdd92ac9ceaef90e40f78599f9109f2f345252e0ac9d98e7e084@<gitbox.activemq.apache.org>
- thread.html/33c6bccfeb7adf644d4d79894ca8f09370be6ed4b20632c2e228d085@<commits.cassandra.apache.org>
- thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@<issues.activemq.apache.org>
- thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@<dev.drill.apache.org>
- thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@<dev.drill.apache.org>
- thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@<issues.drill.apache.org>
- thread.html/r27eb79a87a760335226dbfa6a7b7bffea539a535f8e80c41e482106d@<dev.cxf.apache.org>