[Snyk] Security upgrade commons-collections:commons-collections from 3.1 to 3.2.2

[samsnyk]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• log4shell-goof/log4shell-server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Deserialization of Untrusted Data SNYK-JAVA-COMMONSCOLLECTIONS-6056408	921	commons-collections:commons-collections: 3.1 -> 3.2.2 No Path Found Mature

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Deserialization of Untrusted Data

[samsnyk]

This upgrade from version 3.1 to 3.2.2 includes bug fixes and a critical security patch. While version 3.2 was documented as being fully binary compatible with 3.1, version 3.2.2 introduces a behavioral change that could impact specific use cases. [4]

Key Change:

• Security Fix (Behavioral Change): To mitigate a remote code execution vulnerability, version 3.2.2 disables the serialization of unsafe classes within the functor package by default. [1, 2, 5] Attempts to serialize or deserialize these specific classes (like InvokerTransformer) will now throw an exception where they previously did not. [5, 7]

Deprecations:

• Version 3.2 deprecated BeanMap and MultiHashMap, noting they would be removed in version 4.0. This is not a breaking change for the 3.x version line. [4]

Recommendation:
This is a MEDIUM risk upgrade. While most applications will be unaffected, you must verify that your application does not rely on serializing or deserializing objects from the org.apache.commons.collections.functor package. If it does, you may need to enable the old behavior via a system property, though this is not recommended due to security implications. [1]

Source: Apache Commons Collections Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.