[Snyk] Security upgrade net.logstash.logback:logstash-logback-encoder from 4.11 to 9.0

[officialmofabs]

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/java-pkmst/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	445	net.logstash.logback:logstash-logback-encoder: 4.11 -> 9.0 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:

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	maven/​org.springframework.boot/​spring-boot-test@​2.5.14
	maven/​org.junit.jupiter/​junit-jupiter-api@​5.10.2
	maven/​org.apache.maven/​maven-core@​3.9.6
	maven/​jakarta.validation/​jakarta.validation-api@​2.0.2
	maven/​org.codehaus.janino/​janino@​3.1.9
	maven/​com.googlecode.lambdaj/​lambdaj@​2.3.3
	maven/​io.airlift/​airline@​0.9
	maven/​org.mockito/​mockito-core@​4.10.0
	maven/​org.codehaus.plexus/​plexus-utils@​3.5.1
	maven/​org.codehaus.plexus/​plexus-archiver@​4.8.0
	maven/​org.apache.maven/​maven-compat@​3.9.6
	maven/​org.testng/​testng@​7.10.2
	maven/​io.springfox/​springfox-swagger2@​3.0.0
	maven/​org.apache.maven.plugin-testing/​maven-plugin-testing-harness@​3.3.0
	maven/​org.apache.maven.shared/​maven-verifier@​1.8.0
	maven/​org.apache.maven/​maven-resolver-provider@​3.9.6
	maven/​org.springframework.boot/​spring-boot-starter-test@​2.5.14
	maven/​org.sonatype.plexus/​plexus-build-api@​0.0.7
	maven/​org.apache.maven/​maven-plugin-api@​3.9.6
	maven/​org.apache.maven/​maven-artifact@​3.9.6
	maven/​org.apache.maven.plugin-tools/​maven-plugin-annotations@​3.9.0
	maven/​org.springframework.boot/​spring-boot-starter-web@​2.5.14

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		maven/org.springframework/spring-web@5.3.20 has a Critical CVE. CVE: GHSA-4wrc-f8pq-fpqp Pivotal Spring Framework contains unsafe Java deserialization methods (CRITICAL) Affected versions: < 6.0.0 Patched version: 6.0.0 From: pom.xml → maven/org.springframework.boot/spring-boot-starter-web@2.5.14 → maven/org.springframework/spring-web@5.3.20 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.springframework/spring-web@5.3.20. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		maven/org.springframework/spring-webmvc@5.3.20 has a Critical CVE. CVE: GHSA-7phw-cxx7-q9vq Spring Framework is vulnerable to security bypass via mvcRequestMatcher pattern mismatch (CRITICAL) Affected versions: >= 6.0.0 < 6.0.7; >= 5.3.0 < 5.3.26 Patched version: 5.3.26 From: pom.xml → maven/org.springframework.boot/spring-boot-starter-web@2.5.14 → maven/org.springframework/spring-webmvc@5.3.20 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.springframework/spring-webmvc@5.3.20. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • OpenAPI Generator
  • Linux tests
  • Windows tests
  • .github/workflows/samples-r.yaml

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #706 at branch `snyk-fix-85af49ac6ef30b26a7fc1e243edf3945`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}