com.google.guava:guava@18.0-rc1 vulnerabilities
-
latest version
33.3.1-jre
-
latest non vulnerable version
-
first published
15 years ago
-
latest version published
2 months ago
-
licenses detected
- [10.0-rc1,)
-
package manager
Direct Vulnerabilities
Known vulnerabilities in the com.google.guava:guava package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
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 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 |
[,32.0.0-android)
(32.0.0-android,32.0.0-jre)
|
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 How to fix Information Disclosure? There is no fix for |
[,30.0-android)
(30.0-android,30.0-jre)
|
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:
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 |
[11.0,24.1.1)
(24.1.1-android,24.1.1-jre)
|