com.google.guava:guava 23.1-android vulnerabilities

Known vulnerabilities in the com.google.guava:guava package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
L Creation of Temporary File in Directory with Insecure Permissions com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more. Affected versions of this package are vulnerable to Creation of Temporary File in Directory with Insecure Permissions due to the use of Java's default temporary directory for file creation in `FileBackedOutputStream`. Other users and apps on the machine with access to the default Java temporary directory can access the files created by this class. This more fully addresses the underlying issue described in CVE-2020-8908, by deprecating the permissive temp file creation behavior. NOTE: Even though the security vulnerability is fixed in version 32.0.0, the maintainers recommend using version 32.0.1, as version 32.0.0 breaks some functionality under Windows. How to fix Creation of Temporary File in Directory with Insecure Permissions? Upgrade `com.google.guava:guava` to version 32.0.0-android, 32.0.0-jre or higher.	[,32.0.0-android)(32.0.0-android,32.0.0-jre)
L Information Disclosure com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more. Affected versions of this package are vulnerable to Information Disclosure. The file permissions on the file created by `com.google.common.io.Files.createTempDir` allow an attacker running a malicious program co-resident on the same machine to steal secrets stored in this directory. This is because, by default, on unix-like operating systems the /tmp directory is shared between all users, so if the correct file permissions aren't set by the directory/file creator, the file becomes readable by all other users on that system. How to fix Information Disclosure? There is no fix for `com.google.guava:guava`. However, in version 30.0 and above, the vulnerable functionality has been deprecated. In oder to mitigate this vulnerability, upgrade to version 30.0 or higher and ensure your dependencies don't use the createTempDir or createTempFile methods.	[,30.0-android)(30.0-android,30.0-jre)
M Deserialization of Untrusted Data com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more. Affected versions of this package are vulnerable to Deserialization of Untrusted Data. During deserialization, two Guava classes accept a caller-specified size parameter and eagerly allocate an array of that size: `AtomicDoubleArray` (when serialized with Java serialization) `CompoundOrdering` (when serialized with GWT serialization) An attacker may be able to send a specially crafted request which with then cause the server to allocate all it's memory, without validation whether the data size is reasonable. How to fix Deserialization of Untrusted Data? Upgrade `com.google.guava:guava` to version 24.1.1, 24.1.1-jre or higher.	[11.0,24.1.1)(24.1.1-android,24.1.1-jre)

Vulnerability

Vulnerable Version

Creation of Temporary File in Directory with Insecure Permissions

com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.

Affected versions of this package are vulnerable to Creation of Temporary File in Directory with Insecure Permissions due to the use of Java's default temporary directory for file creation in FileBackedOutputStream. Other users and apps on the machine with access to the default Java temporary directory can access the files created by this class. This more fully addresses the underlying issue described in CVE-2020-8908, by deprecating the permissive temp file creation behavior.

NOTE: Even though the security vulnerability is fixed in version 32.0.0, the maintainers recommend using version 32.0.1, as version 32.0.0 breaks some functionality under Windows.

How to fix Creation of Temporary File in Directory with Insecure Permissions?

Upgrade com.google.guava:guava to version 32.0.0-android, 32.0.0-jre or higher.

[,32.0.0-android)(32.0.0-android,32.0.0-jre)

Information Disclosure

Affected versions of this package are vulnerable to Information Disclosure. The file permissions on the file created by com.google.common.io.Files.createTempDir allow an attacker running a malicious program co-resident on the same machine to steal secrets stored in this directory. This is because, by default, on unix-like operating systems the /tmp directory is shared between all users, so if the correct file permissions aren't set by the directory/file creator, the file becomes readable by all other users on that system.

How to fix Information Disclosure?

There is no fix for com.google.guava:guava. However, in version 30.0 and above, the vulnerable functionality has been deprecated. In oder to mitigate this vulnerability, upgrade to version 30.0 or higher and ensure your dependencies don't use the createTempDir or createTempFile methods.

[,30.0-android)(30.0-android,30.0-jre)

Deserialization of Untrusted Data

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. During deserialization, two Guava classes accept a caller-specified size parameter and eagerly allocate an array of that size:

AtomicDoubleArray (when serialized with Java serialization)
CompoundOrdering (when serialized with GWT serialization)

An attacker may be able to send a specially crafted request which with then cause the server to allocate all it's memory, without validation whether the data size is reasonable.

How to fix Deserialization of Untrusted Data?

Upgrade com.google.guava:guava to version 24.1.1, 24.1.1-jre or higher.

[11.0,24.1.1)(24.1.1-android,24.1.1-jre)

com.google.guava:guava@23.1-android vulnerabilities

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package manager

Direct Vulnerabilities

How to fix?