Denial of Service in Google Guava
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.google.guava:guava Maven |
|
|
| com.google.guava:guava-jdk5 Maven |
| No fix yet |
| com.googlecode.guava-osgi:guava-osgi Maven |
| Product | Affected | Fixed in |
|---|---|---|
| com.google.guava:guava Maven |
|
|
| com.google.guava:guava-jdk5 Maven |
| No fix yet |
| com.googlecode.guava-osgi:guava-osgi Maven |
≤ 11.0.1| No fix yet |
| de.mhus.ports:vaadin-shared-deps Maven |
| No fix yet |
| org.hudsonci.lib.guava:guava Maven |
| No fix yet |
| org.sonatype.sisu:sisu-guava Maven |
| No fix yet |
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.
From the CVE record · mitre
Affected Guava classes can allocate unbounded memory while deserializing attacker-provided data. A remote attacker can cause denial of service against a server that depends on the library and deserializes that data using Java serialization for AtomicDoubleArray or GWT serialization for CompoundOrdering. The input does not specify whether authentication is required.
Engineers running servers with Maven com.google.guava:guava versions >=11.0 and <24.1.1-android, or the listed affected versions of guava-jdk5, guava-osgi, vaadin-shared-deps, org.hudsonci.lib.guava:guava, or sisu-guava, should check their dependencies.