Skip to content
This repository was archived by the owner on Feb 5, 2026. It is now read-only.

Comments

[Snyk] Fix for 1 vulnerabilities#45

Open
ayusuf-mq wants to merge 1 commit intomasterfrom
snyk-fix-ebabaeb2a765f9fa2267f4fd9ca99c0a
Open

[Snyk] Fix for 1 vulnerabilities#45
ayusuf-mq wants to merge 1 commit intomasterfrom
snyk-fix-ebabaeb2a765f9fa2267f4fd9ca99c0a

Conversation

@ayusuf-mq
Copy link

snyk-top-banner

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

Snyk changed the following file(s):

  • samples/server/petstore/jaxrs-cxf/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
low severity External Initialization of Trusted Variables or Data Stores
SNYK-JAVA-CHQOSLOGBACK-15062482
  290   ch.qos.logback:logback-classic:
1.2.0 -> 1.5.25
ch.qos.logback:logback-core:
1.2.0 -> 1.5.25
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:

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

@ayusuf-mq
Copy link
Author

Merge Risk: High

This upgrade from Logback 1.2.0 to 1.5.25 is a major update with significant breaking changes. It requires updates to core dependencies (SLF4J and Java), and may break existing configurations, especially those using optional components or programmatic setup.

Highlights:

  • SLF4J 2.x Required: Logback 1.3.x and newer require SLF4J 2.0.x, which is not backward compatible with the SLF4J 1.7.x used by Logback 1.2.x. This is a common cause of logging failures after the upgrade.
  • Java 11 Required: Logback 1.4.x and newer require Java 11 at runtime, an increase from Java 8 required for version 1.3.x.
  • Java EE to Jakarta EE Namespace Change: Optional components like SMTPAppender switched from the javax.* (Java EE) namespace to jakarta.* (Jakarta EE) in version 1.4.x. This will break applications using these appenders on modern application servers.
  • Internal API Changes: Logback's internal configuration system, Joran, was rewritten in version 1.3. Code that programmatically configures Logback or extends internal classes may need to be adapted. Additionally, classes like JaninoEventEvaluator were removed in later versions.

Source: Logback documentation and release notes.
Recommendation: Before merging, verify the SLF4J version across the entire project to ensure compatibility. Update the runtime to Java 11. Check for usage of any optional components that now depend on the Jakarta EE namespace and for any programmatic configuration that may rely on changed internal APIs.

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants