[Snyk] Fix for 7 vulnerabilities

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • spring-ws-security/pom.xml

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	596/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.5	Information Disclosure SNYK-JAVA-COMGOOGLEGUAVA-1015415		No	Proof of Concept
	479/1000 Why? Has a fix available, CVSS 5.3	Improper Input Validation SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-1048058		No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Improper Input Validation SNYK-JAVA-ORGAPACHESANTUARIO-1655558		No	No Known Exploit
	434/1000 Why? Has a fix available, CVSS 4.4	Privilege Escalation SNYK-JAVA-ORGSPRINGFRAMEWORK-1296829	org.springframework.ws:spring-ws-core: 3.1.0-SNAPSHOT -> 3.1.0	No	No Known Exploit
	429/1000 Why? Has a fix available, CVSS 4.3	Improper Output Neutralization for Logs SNYK-JAVA-ORGSPRINGFRAMEWORK-2329097	org.springframework.ws:spring-ws-core: 3.1.0-SNAPSHOT -> 3.1.0 org.springframework.ws:spring-xml: 3.1.0-SNAPSHOT -> 3.1.0	No	No Known Exploit
	429/1000 Why? Has a fix available, CVSS 4.3	Improper Input Validation SNYK-JAVA-ORGSPRINGFRAMEWORK-2330878	org.springframework.ws:spring-ws-core: 3.1.0-SNAPSHOT -> 3.1.0 org.springframework.ws:spring-xml: 3.1.0-SNAPSHOT -> 3.1.0	No	No Known Exploit
	439/1000 Why? Has a fix available, CVSS 4.5	Privilege Escalation SNYK-JAVA-ORGSPRINGFRAMEWORKSECURITY-1078232		No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade org.apache.santuario:xmlsec@2.2.0 to org.apache.santuario:xmlsec@2.2.3; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/apache/wss4j/wss4j-parent/2.3.0/wss4j-parent-2.3.0.pom
  • Could not upgrade org.apache.wss4j:wss4j-ws-security-dom@2.3.0 to org.apache.wss4j:wss4j-ws-security-dom@2.3.2; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location
  • Could not upgrade org.springframework.security:spring-security-core@5.4.1 to org.springframework.security:spring-security-core@5.5.4; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/security/spring-security-bom/5.4.1/spring-security-bom-5.4.1.pom
  • Could not upgrade org.springframework:spring-beans@5.3.1 to org.springframework:spring-beans@5.3.14; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/spring-framework-bom/5.3.1/spring-framework-bom-5.3.1.pom
  • Could not upgrade org.springframework:spring-core@5.3.1 to org.springframework:spring-core@5.3.14; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/spring-framework-bom/5.3.1/spring-framework-bom-5.3.1.pom
  • Could not upgrade org.springframework:spring-tx@5.3.1 to org.springframework:spring-tx@5.3.14; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/spring-framework-bom/5.3.1/spring-framework-bom-5.3.1.pom

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic