[Snyk] Fix for 1 vulnerabilities

[catejst]

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

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Uncontrolled Resource Consumption SNYK-JAVA-COMMONSIO-8161190	545	commons-io:commons-io: 2.5 -> 2.14.0 org.zeroturnaround:zt-exec: 1.9 -> 1.11 No Path Found No Known Exploit

---

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:

🦉 Uncontrolled Resource Consumption

[guardrails]

⚠️ We detected 9 security issues in this pull request:

Vulnerable Libraries (9)

Severity	Details
Medium	pkg:maven/org.springframework.data/[email protected] (t) upgrade to: 1.11.20,2.0.14,2.1.6
Medium	pkg:maven/org.springframework/[email protected] (t) upgrade to: 6.0.7,5.3.26,5.2.23.RELEASE
High	pkg:maven/ch.qos.logback/[email protected] (t) upgrade to: 1.3.12,1.4.12,1.2.13
High	pkg:maven/org.hibernate/[email protected] (t) upgrade to: 5.4.24.Final,5.3.20.Final
Critical	pkg:maven/dom4j/[email protected] (t) upgrade to: 2.0.3,2.1.3
N/A	pkg:maven/org.apache.tomcat.embed/[email protected] (t) upgrade to: 11.0.0-M17,10.1.19,9.0.86,8.5.99
High	pkg:maven/org.springframework/[email protected] (t) upgrade to: 5.2.22.RELEASE,5.3.20
Critical	pkg:maven/org.springframework/[email protected] (t) upgrade to: 5.3.18,2.5.12,2.6.6,5.2.20
High	pkg:maven/org.springframework/[email protected] (t) upgrade to: 5.3.19,5.2.21

More info on how to fix Vulnerable Libraries in Java.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
maven/commons-io/[email protected]	eval, filesystem, network, shell, unsafe Transitive: environment	+301	374 MB
maven/org.zeroturnaround/[email protected]	eval, filesystem, shell Transitive: environment, network, unsafe	+300	372 MB

🚮 Removed packages: maven/commons-io/[email protected], maven/org.zeroturnaround/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	maven/log4j/[email protected]	CVE: GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j (CRITICAL) Affected versions: >= 1.2, <= 1.2.17 Patched version: No patched versions	pom.xml	⚠︎
Critical CVE	maven/log4j/[email protected]	CVE: GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x (CRITICAL) Affected versions: <= 2.0 Patched version: No patched versions	pom.xml	⚠︎
Critical CVE	maven/log4j/[email protected]	CVE: GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j (CRITICAL) Affected versions: <= 2.0 Patched version: No patched versions	pom.xml	⚠︎
Critical CVE	maven/commons-collections/[email protected]	CVE: GHSA-fjq5-5j5f-mvxh Deserialization of Untrusted Data in Apache commons collections (CRITICAL) Affected versions: >= 3.2.1, < 3.2.2 Patched version: No patched versions	pom.xml	⚠︎
Critical CVE	maven/org.springframework/[email protected]	CVE: GHSA-36p3-wjmg-h94x Remote Code Execution in Spring Framework (CRITICAL) Affected versions: < 5.2.20.RELEASE Patched version: 5.2.20.RELEASE	pom.xml	⚠︎
Critical CVE	maven/org.quartz-scheduler/[email protected]	CVE: GHSA-9qcf-c26r-x5rf XML external entity injection in Terracotta Quartz Scheduler (CRITICAL) Affected versions: < 2.3.2 Patched version: 2.3.2	pom.xml	⚠︎
Critical CVE	maven/org.apache.derby/[email protected]_1	CVE: GHSA-rcjc-c4pj-xxrp Apache Derby: LDAP injection vulnerability in authenticator (CRITICAL) Affected versions: >= 10.1.1.0, < 10.14.3 Patched version: 10.14.3	pom.xml	⚠︎
Critical CVE	maven/org.apache.derby/[email protected]_1	CVE: GHSA-wr69-g62g-2r9h Improper Restriction of XML External Entity Reference in Apace Derby (CRITICAL) Affected versions: <= 10.11.1.1 Patched version: 10.12.1.1	pom.xml	⚠︎
Critical CVE	maven/com.h2database/[email protected]	CVE: GHSA-45hx-wfhj-473x Arbitrary code execution in H2 Console (CRITICAL) Affected versions: < 2.1.210 Patched version: 2.1.210	pom.xml	⚠︎
Critical CVE	maven/dom4j/[email protected]	CVE: GHSA-hwj3-m3p6-hj38 dom4j allows External Entities by default which might enable XXE attacks (CRITICAL) Affected versions: <= 1.6.1 Patched version: No patched versions	pom.xml	⚠︎
Critical CVE	maven/com.thoughtworks.xstream/[email protected]	CVE: GHSA-f554-x222-wgf7 Command Injection in Xstream (CRITICAL) Affected versions: < 1.4.7 Patched version: 1.4.7	pom.xml	⚠︎
Critical CVE	maven/com.thoughtworks.xstream/[email protected]	CVE: GHSA-hf23-9pf7-388p Deserialization of Untrusted Data and Code Injection in xstream (CRITICAL) Affected versions: <= 1.4.10 Patched version: 1.4.11	pom.xml	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore maven/log4j/[email protected]
• @SocketSecurity ignore maven/commons-collections/[email protected]
• @SocketSecurity ignore maven/org.springframework/[email protected]
• @SocketSecurity ignore maven/org.quartz-scheduler/[email protected]
• @SocketSecurity ignore maven/org.apache.derby/[email protected]_1
• @SocketSecurity ignore maven/com.h2database/[email protected]
• @SocketSecurity ignore maven/dom4j/[email protected]
• @SocketSecurity ignore maven/com.thoughtworks.xstream/[email protected]