[PLUGIN-1915]: Fix CVEs in com.google.guava:31.1-jre #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
Guava (com.google.guava:31.1-jre): 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.
Root Cause:
Guava : FileBackedOutputStream uses temporary files to store data once a certain memory threshold is exceeded. This can result in failure to sufficiently restrict access to the temp file, making it susceptible to race conditions or file hijacking. It can further allow unauthorized access or modification of the temporary file by other processes/users on the system.
Fix:
Add the guava dependency to the exclusions and upgrade to a higher version such as 33.4.0-jre to get rid of the CVE.
JIRA : PLUGIN-1915