Bump the maven group across 1 directory with 5 updates

[dependabot]

Bumps the maven group with 5 updates in the /java directory:

Package	From	To
com.google.guava:guava	30.1.1-jre	32.0.0-jre
com.google.protobuf:protobuf-java	3.19.4	3.25.5
commons-io:commons-io	2.7	2.14.0
io.netty:netty-handler	4.1.72.Final	4.1.118.Final
org.apache.logging.log4j:log4j-core	2.17.1	2.25.4

Updates com.google.guava:guava from 30.1.1-jre to 32.0.0-jre

Release notes

Sourced from com.google.guava:guava's releases.

32.0.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>32.0.0-jre</version>
  <!-- or, for Android: -->
  <version>32.0.0-android</version>
</dependency>

Jar files

• 32.0.0-jre.jar
• 32.0.0-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 32.0.0-jre
• 32.0.0-android

JDiff

• 32.0.0-jre vs. 31.1-jre
• 32.0.0-android vs. 31.1-android
• 32.0.0-android vs. 32.0.0-jre

Changelog

Security fixes

• Reimplemented Files.createTempDir and FileBackedOutputStream to further address CVE-2020-8908 (#4011) and CVE-2023-2976 (#2575). (feb83a1c8f)

While CVE-2020-8908 was officially closed when we deprecated Files.createTempDir in Guava 30.0, we've heard from users that even recent versions of Guava have been listed as vulnerable in other databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used FileBackedOutputStream class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under "Incompatible changes" below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to 32.0.1 which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we warn that common.io in particular may not work under Windows, we didn't intend to regress support.) Sorry for the trouble.

Incompatible changes

Although this release bumps Guava's major version number, it makes no binary-incompatible changes to the guava artifact.

One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:

• The new implementations of Files.createTempDir and FileBackedOutputStream throw an exception under Windows. This is fixed in 32.0.1. Sorry for the trouble.
• guava-gwt now requires GWT 2.10.0.
• This release makes a binary-incompatible change to a @Beta API in the separate artifact guava-testlib. Specifically, we changed the return type of TestingExecutors.sameThreadScheduledExecutor to ListeningScheduledExecutorService. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)

... (truncated)

Commits

• See full diff in compare view

Updates com.google.protobuf:protobuf-java from 3.19.4 to 3.25.5

Commits

• 9d0ec0f Updating version.json and repo version numbers to: 25.5
• 4a197e7 Merge pull request #18387 from protocolbuffers/cp-lp-25
• b5a7cf7 Remove RecursiveGroup test case which doesn't exist in 25.x pre-Editions
• f000b7e Fix merge conflict by adding optional label to proto2 unittest_lite.proto
• 4728531 Add recursion check when parsing unknown fields in Java.
• 850fcce Internal change
• b704498 Internal change
• e673479 Fix cord handling in DynamicMessage and oneofs. (#18375)
• 8a60b65 Merge pull request #17704 from protocolbuffers/cp-segv
• 94a2663 Fixed a SEGV when deep copying a non-reified sub-message.
• Additional commits viewable in compare view

Updates commons-io:commons-io from 2.7 to 2.14.0

Updates io.netty:netty-handler from 4.1.72.Final to 4.1.118.Final

Commits

• 36f95cf [maven-release-plugin] prepare release netty-4.1.118.Final
• 87f4072 Merge commit from fork
• d1fbda6 Merge commit from fork
• f844d78 Upgrade netty-tcnative to 2.0.70.Final (#14790)
• 8afb5d9 Only run 2 jobs with leak detection to minimize build times (#14784)
• f2c27da AdaptivePoolingAllocator: Round chunk sizes up to MIN_CHUNK_SIZE units and re...
• 8d387ff Change the default AdaptiveRecvByteBufAllocator buffer size values' visibilit...
• 1cfd3a6 Fix possible buffer leak when stream can't be mapped (#14746)
• 8f9eadb Fix AccessControlException in GlobalEventExecutor (#14743)
• 6fcd3e6 KQueueEventLoop leaks memory on shutdown. (#14745)
• Additional commits viewable in compare view

Updates org.apache.logging.log4j:log4j-core from 2.17.1 to 2.25.4

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.