[Snyk] Security upgrade org.hibernate:hibernate-validator from 4.3.1.Final to 6.2.0.Final

[philvarner-snyk]

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

Snyk changed the following file(s):

• todolist-goof/todolist-web-common/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Arbitrary Code Injection SNYK-JAVA-ORGHIBERNATE-15702517	156	org.hibernate:hibernate-validator: 4.3.1.Final -> 6.2.0.Final Major version upgrade No Path Found No Known Exploit
	Cross-site Scripting (XSS) SNYK-JAVA-ORGHIBERNATE-15702518	99	org.hibernate:hibernate-validator: 4.3.1.Final -> 6.2.0.Final Major version upgrade No Path Found No Known Exploit

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:

🦉 Arbitrary Code Injection
🦉 Cross-site Scripting (XSS)

[philvarner-snyk]

This is a major upgrade from version 4.3.1.Final to 6.2.0.Final, spanning two major releases (v5 and v6) and two new specification versions (Bean Validation 1.1 and 2.0). This upgrade includes significant breaking changes that will require code and build configuration modifications.

Key Breaking Changes:

• Maven Coordinates Change: The Maven groupId has changed. You must update your build configuration from org.hibernate to org.hibernate.validator for all Hibernate Validator artifacts starting with version 6.0.
• Java and Specification Requirements: The upgrade requires a move from Java 6 to at least Java 8. It also adopts the Bean Validation 2.0 specification, which introduces new features but also deprecates and removes old ones.
• API Removals: APIs and classes that were deprecated in versions 4.x and 5.x have been removed. This notably includes the old proprietary method validation API, which was replaced by the standardized version in Bean Validation 1.1.
• Expression Language (EL) Security Hardening: Starting in version 6.2, Expression Language is disabled by default for custom validation messages for security reasons. Code that relies on EL in custom violations will need to be updated to explicitly enable it on a case-by-case basis.
• Dependency Changes: The CDI integration has been extracted into a separate artifact, org.hibernate:hibernate-validator-cdi, which must be added as a dependency if used. An Expression Language 3.0 implementation is also now a required dependency.

Recommendation:

This is a high-impact upgrade. It is critical to first update the Maven groupId in your build files. Then, thoroughly review your code for usage of any removed APIs and for any custom validation logic that uses Expression Language, as it will likely need modification. Due to the number of major changes, extensive testing will be required.

Source: Hibernate Validator Migration Guide

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

[philvarner-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.