[Snyk] Security upgrade ch.qos.logback:logback-classic from 1.4.7 to 1.5.14

[robfrank]

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
	External Initialization of Trusted Variables or Data Stores SNYK-JAVA-CHQOSLOGBACK-13169722	581	ch.qos.logback:logback-classic: 1.4.7 -> 1.5.14 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @robfrank, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This PR, automatically generated by Snyk, upgrades the ch.qos.logback:logback-classic dependency from version 1.4.7 to 1.5.14 to fix a security vulnerability (SNYK-JAVA-CHQOSLOGBACK-13169722) related to 'External Initialization of Trusted Variables or Data Stores'. The change is limited to updating the version property in pom.xml.

Highlights

• Security Upgrade: This pull request is an automated security upgrade initiated by Snyk to address a medium-severity vulnerability in the logback-classic library.
• Dependency Update: The logback-classic dependency has been updated from version 1.4.7 to 1.5.14.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, addresses a security vulnerability by upgrading logback-classic. While this is a crucial update, I've identified a potential issue with a transitive dependency that should be addressed to prevent possible runtime errors. Please see my detailed comment below.

[gemini-code-assist]

While upgrading logback-classic is important for security, this change introduces a potential dependency version mismatch.

The new version ch.qos.logback:logback-classic:1.5.14 depends on org.slf4j:slf4j-api:2.0.13. However, this project explicitly defines slf4j-api.version as 2.0.7 (on line 36), which will override the transitive dependency version due to Maven's dependency mediation.

Using an older version of slf4j-api than what logback-classic was built and tested against can lead to subtle bugs or runtime errors like NoSuchMethodError if logback-classic uses APIs introduced in slf4j-api after version 2.0.7.

To ensure compatibility and follow dependency management best practices, I recommend aligning the slf4j-api version. Please update the slf4j-api.version property on line 36 to 2.0.13.