[Snyk] Fix for 1 vulnerabilities

[officialmofabs]

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

Snyk changed the following file(s):

• samples/client/petstore/java/jersey2-java8/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Race Condition SNYK-JAVA-ORGGLASSFISHJERSEYCORE-14049172	863	org.glassfish.jersey.connectors:jersey-apache-connector: 2.37 -> 2.46 org.glassfish.jersey.core:jersey-client: 2.37 -> 2.46 Proof of Concept

---

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:

🦉 Race Condition

[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/​com.h2database/​h2@​1.4.196
	maven/​io.springfox/​springfox-swagger-ui@​2.6.0
	maven/​org.springframework.security.oauth/​spring-security-oauth2@​2.0.14.RELEASE
	maven/​org.jolokia/​jolokia-core@​1.3.7
	maven/​com.jayway.restassured/​rest-assured@​2.9.0
	maven/​net.logstash.logback/​logstash-logback-encoder@​4.11
	maven/​org.springframework/​spring-jdbc@​4.3.10.RELEASE
	maven/​org.springframework/​spring-test@​4.3.10.RELEASE
	maven/​info.cukes/​cucumber-java@​1.2.5
	maven/​commons-logging/​commons-logging@​1.2
	maven/​org.threeten/​threetenbp@​1.4.0
	maven/​org.springframework.boot/​spring-boot-starter-security@​1.5.6.RELEASE
	maven/​org.springframework.boot/​spring-boot-starter-remote-shell@​1.5.6.RELEASE
	maven/​org.springframework.boot/​spring-boot-starter-jetty@​1.5.6.RELEASE
	maven/​com.netflix.hystrix/​hystrix-javanica@​1.4.1
	maven/​info.cukes/​cucumber-spring@​1.2.5
	maven/​org.springframework.boot/​spring-boot-starter-actuator@​1.5.6.RELEASE
	maven/​jakarta.annotation/​jakarta.annotation-api@​1.3.5
	maven/​info.cukes/​cucumber-junit@​1.2.5
	maven/​com.github.tomakehurst/​wiremock@​1.46
	maven/​net.masterthought/​cucumber-reporting@​3.10.0
	maven/​io.gatling.highcharts/​gatling-charts-highcharts@​2.3.0

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		Critical CVE: Policies not properly enforced in OWASP Java HTML Sanitizer in maven com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer CVE: GHSA-3w73-fmf3-hg5c Policies not properly enforced in OWASP Java HTML Sanitizer (CRITICAL) Affected versions: < 20211018.1 Patched version: 20211018.1 From: pom.xml → maven/net.masterthought/cucumber-reporting@3.10.0 → maven/com.googlecode.owasp-java-html-sanitizer/owasp-java-html-sanitizer@20170515.1 ℹ 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/com.googlecode.owasp-java-html-sanitizer/owasp-java-html-sanitizer@20170515.1. 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		Critical CVE: Arbitrary code execution in H2 Console in maven com.h2database:h2 CVE: GHSA-45hx-wfhj-473x Arbitrary code execution in H2 Console (CRITICAL) Affected versions: < 2.1.210 Patched version: 2.1.210 From: samples/server/petstore/java-pkmst/pom.xml → maven/com.h2database/h2@1.4.196 ℹ 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/com.h2database/h2@1.4.196. 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		Critical CVE: RCE in H2 Console in maven com.h2database:h2 CVE: GHSA-h376-j262-vhq6 RCE in H2 Console (CRITICAL) Affected versions: >= 1.1.100 < 2.0.206 Patched version: 2.0.206 From: samples/server/petstore/java-pkmst/pom.xml → maven/com.h2database/h2@1.4.196 ℹ 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/com.h2database/h2@1.4.196. 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		Critical CVE: Deserialization of Untrusted Data in Apache commons collections in maven commons-collections:commons-collections CVE: GHSA-fjq5-5j5f-mvxh Deserialization of Untrusted Data in Apache commons collections (CRITICAL) Affected versions: < 3.2.2 Patched version: 3.2.2 From: pom.xml → maven/com.netflix.hystrix/hystrix-javanica@1.4.1 → maven/commons-collections/commons-collections@3.2.1 ℹ 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/commons-collections/commons-collections@3.2.1. 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		Critical CVE: Cross-site scripting in Swagger-UI in maven io.springfox:springfox-swagger-ui CVE: GHSA-c427-hjc3-wrfw Cross-site scripting in Swagger-UI (CRITICAL) Affected versions: < 2.10.0 Patched version: 2.10.0 From: samples/server/petstore/java-pkmst/pom.xml → maven/io.springfox/springfox-swagger-ui@2.6.0 ℹ 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/io.springfox/springfox-swagger-ui@2.6.0. 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		Critical CVE: Deserialization of Untrusted Data in Log4j in maven log4j:log4j CVE: GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j (CRITICAL) Affected versions: >= 1.2 <= 1.2.17 Patched version: No patched versions From: pom.xml → maven/com.github.tomakehurst/wiremock@1.46 → maven/log4j/log4j@1.2.16 ℹ 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/log4j/log4j@1.2.16. 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		Critical CVE: SQL Injection in Log4j 1.2.x in maven log4j:log4j CVE: GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x (CRITICAL) Affected versions: <= 1.2.17 Patched version: No patched versions From: pom.xml → maven/com.github.tomakehurst/wiremock@1.46 → maven/log4j/log4j@1.2.16 ℹ 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/log4j/log4j@1.2.16. 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		Critical CVE: Deserialization of Untrusted Data in Apache Log4j in maven log4j:log4j CVE: GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j (CRITICAL) Affected versions: <= 1.2.17 Patched version: No patched versions From: pom.xml → maven/com.github.tomakehurst/wiremock@1.46 → maven/log4j/log4j@1.2.16 ℹ 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/log4j/log4j@1.2.16. 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		Critical CVE: Incomplete fix for Apache Log4j vulnerability in maven org.apache.logging.log4j:log4j-core CVE: GHSA-7rjr-3q55-vv33 Incomplete fix for Apache Log4j vulnerability (CRITICAL) Affected versions: >= 2.13.0 < 2.16.0; < 2.12.2 Patched version: 2.12.2 From: pom.xml → maven/net.masterthought/cucumber-reporting@3.10.0 → maven/org.apache.logging.log4j/log4j-core@2.8.2 ℹ 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.apache.logging.log4j/log4j-core@2.8.2. 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		Critical CVE: Remote code injection in Log4j in maven org.apache.logging.log4j:log4j-core CVE: GHSA-jfh8-c2jp-5v3q Remote code injection in Log4j (CRITICAL) Affected versions: >= 2.13.0 < 2.15.0; >= 2.0-beta9 < 2.3.1; >= 2.4 < 2.12.2 Patched version: 2.12.2 From: pom.xml → maven/net.masterthought/cucumber-reporting@3.10.0 → maven/org.apache.logging.log4j/log4j-core@2.8.2 ℹ 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.apache.logging.log4j/log4j-core@2.8.2. 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		Critical CVE: Deserialization of Untrusted Data in maven org.codehaus.jackson:jackson-mapper-asl CVE: GHSA-c27h-mcmw-48hv Deserialization of Untrusted Data in org.codehaus.jackson:jackson-mapper-asl (CRITICAL) Affected versions: <= 1.9.13 Patched version: No patched versions From: pom.xml → maven/org.springframework.security.oauth/spring-security-oauth2@2.0.14.RELEASE → maven/org.codehaus.jackson/jackson-mapper-asl@1.9.13 ℹ 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.codehaus.jackson/jackson-mapper-asl@1.9.13. 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		Critical CVE: Spring Security OAuth vulnerable to remote code execution (RCE) in maven org.springframework.security.oauth:spring-security-oauth2 CVE: GHSA-rrpm-pj7p-7j9q Spring Security OAuth vulnerable to remote code execution (RCE) (CRITICAL) Affected versions: >= 2.3.0 < 2.3.3; >= 2.2.0 < 2.2.2; >= 2.1.0 < 2.1.2; >= 2.0.0 < 2.0.15; >= 1.0.0 <= 1.0.5 Patched version: 2.0.15 From: samples/server/petstore/java-pkmst/pom.xml → maven/org.springframework.security.oauth/spring-security-oauth2@2.0.14.RELEASE ℹ 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.security.oauth/spring-security-oauth2@2.0.14.RELEASE. 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
  • Samples Java Client JDK11
  • Linux tests
  • Windows tests
  • Samples Java Client JDK11
  • .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 #741 at branch `snyk-fix-4c13cbee2b9d8e425c17223fb38a9e2a`

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

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