[Snyk] Fix for 12 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• pom.xml
• todolist-core/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Remote Code Execution SNYK-JAVA-ORGSPRINGFRAMEWORK-2436751	691	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found Mature
	Remote Code Execution (RCE) SNYK-JAVA-ORGHSQLDB-3040860	380	org.hsqldb:hsqldb: 2.3.2 -> 2.7.1 No Path Found No Known Exploit
	SQL Injection SNYK-JAVA-ORGHIBERNATE-584563	167	org.hibernate:hibernate-core: 4.3.7.Final -> 5.3.18.Final org.hibernate:hibernate-entitymanager: 4.3.7.Final -> 5.3.18.Final Major version upgrade No Path Found No Known Exploit
	XML External Entity (XXE) Injection SNYK-JAVA-DOM4J-174153	161	org.hibernate:hibernate-core: 4.3.7.Final -> 5.3.18.Final Major version upgrade No Path Found Proof of Concept
	XML External Entity (XXE) Injection SNYK-JAVA-DOM4J-2812975	150	org.hibernate:hibernate-core: 4.3.7.Final -> 5.3.18.Final Major version upgrade No Path Found No Known Exploit
	Denial of Service (DoS) SNYK-JAVA-ORGSPRINGFRAMEWORK-2823313	91	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found No Known Exploit
	Improper Handling of Case Sensitivity SNYK-JAVA-ORGSPRINGFRAMEWORK-2689634	78	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found Proof of Concept
	Directory Traversal SNYK-JAVA-ORGSPRINGFRAMEWORK-31325	48	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 No Path Found No Known Exploit
	Improper Output Neutralization for Logs SNYK-JAVA-ORGSPRINGFRAMEWORK-2329097	41	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found No Known Exploit
	Improper Input Validation SNYK-JAVA-ORGSPRINGFRAMEWORK-2330878	41	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found No Known Exploit
	Improper Handling of Case Sensitivity SNYK-JAVA-ORGSPRINGFRAMEWORK-8230364	40	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 Major version upgrade No Path Found No Known Exploit
	Improper Handling of Case Sensitivity SNYK-JAVA-ORGSPRINGFRAMEWORK-8230365	40	org.springframework:spring-aspects: 3.2.6.RELEASE -> 3.2.7.RELEASE org.springframework:spring-context: 3.2.6.RELEASE -> 6.1.14 org.springframework:spring-orm: 3.2.6.RELEASE -> 6.1.14 Major version upgrade 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:

🦉 XML External Entity (XXE) Injection
🦉 SQL Injection
🦉 Remote Code Execution (RCE)
🦉 More lessons are available in Snyk Learn

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[snyk-io]

⛔ Snyk checks have failed. 85 issues have been found so far.

Icon	Severity	Issues
	Critical	14
	High	30
	Medium	38
	Low	3

⛔ security/snyk check is complete. 66 issues have been found. (View Details)

⛔ license/snyk check is complete. 19 issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

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