Use of Java's default temporary directory for file creation in FileBackedOutputStream in Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class.
Even though the security vulnerability is fixed in version 32.0.0, maintainers recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows.
A temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava com.google.common.io.Files.createTempDir(). The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method.
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.
Release Notes
google/guava (com.google.guava:guava)
### [`v23.0`](https://togithub.com/google/guava/releases/tag/v23.0): 23.0
Final [Guava 23.0](https://togithub.com/google/guava/wiki/Release23) release.
### [`v22.0`](https://togithub.com/google/guava/releases/tag/v22.0): 22.0
[Compare Source](https://togithub.com/google/guava/compare/v21.0...v22.0)
Final [Guava 22.0](https://togithub.com/google/guava/wiki/Release22) release.
### [`v21.0`](https://togithub.com/google/guava/releases/tag/v21.0): 21.0
[Compare Source](https://togithub.com/google/guava/compare/v20.0...v21.0)
Final [Guava 21.0](https://togithub.com/google/guava/wiki/Release21) release.
This release requires Java 8.
### [`v20.0`](https://togithub.com/google/guava/releases/tag/v20.0): 20.0
[Compare Source](https://togithub.com/google/guava/compare/v19.0...v20.0)
Final [Guava 20.0](https://togithub.com/google/guava/wiki/Release20) release.
### [`v19.0`](https://togithub.com/google/guava/compare/v18.0...v19.0)
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
18.0->32.0.0-androidGitHub Vulnerability Alerts
CVE-2023-2976
Use of Java's default temporary directory for file creation in
FileBackedOutputStreamin Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class.Even though the security vulnerability is fixed in version 32.0.0, maintainers recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows.
CVE-2020-8908
A temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava
com.google.common.io.Files.createTempDir(). The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method.CVE-2018-10237
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.
Release Notes
google/guava (com.google.guava:guava)
### [`v23.0`](https://togithub.com/google/guava/releases/tag/v23.0): 23.0 Final [Guava 23.0](https://togithub.com/google/guava/wiki/Release23) release. ### [`v22.0`](https://togithub.com/google/guava/releases/tag/v22.0): 22.0 [Compare Source](https://togithub.com/google/guava/compare/v21.0...v22.0) Final [Guava 22.0](https://togithub.com/google/guava/wiki/Release22) release. ### [`v21.0`](https://togithub.com/google/guava/releases/tag/v21.0): 21.0 [Compare Source](https://togithub.com/google/guava/compare/v20.0...v21.0) Final [Guava 21.0](https://togithub.com/google/guava/wiki/Release21) release. This release requires Java 8. ### [`v20.0`](https://togithub.com/google/guava/releases/tag/v20.0): 20.0 [Compare Source](https://togithub.com/google/guava/compare/v19.0...v20.0) Final [Guava 20.0](https://togithub.com/google/guava/wiki/Release20) release. ### [`v19.0`](https://togithub.com/google/guava/compare/v18.0...v19.0)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.