[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-webflux from 2.7.17 to 3.3.7

[officialmofabs]

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

Snyk changed the following file(s):

• samples/client/others/java/webclient-useAbstractionForFiles/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Neutralization of Special Elements SNYK-JAVA-CHQOSLOGBACK-8539866	509	org.springframework.boot:spring-boot-starter-webflux: 2.7.17 -> 3.3.7 Major version upgrade No Known Exploit
	Improper Neutralization of Special Elements SNYK-JAVA-CHQOSLOGBACK-8539867	509	org.springframework.boot:spring-boot-starter-webflux: 2.7.17 -> 3.3.7 Major version upgrade No Known Exploit
	Server-side Request Forgery (SSRF) SNYK-JAVA-CHQOSLOGBACK-8539865	334	org.springframework.boot:spring-boot-starter-webflux: 2.7.17 -> 3.3.7 Major version upgrade 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:

🦉 Server-side Request Forgery (SSRF)

Summary by Sourcery

Bug Fixes:

• Upgrade org.springframework.boot:spring-boot-starter-webflux from version 2.7.17 to 3.3.7 to address vulnerabilities related to improper neutralization of special elements and server-side request forgery (SSRF).

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the Spring Boot Starter WebFlux dependency from version 2.7.17 to 3.3.7 in the pom.xml file to address three security vulnerabilities identified by Snyk. The upgrade is a major version change and should be reviewed for compatibility with the existing project setup.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgrade of Spring Boot Starter WebFlux version to address security vulnerabilities.	Updated the Spring Boot version from 2.7.17 to 3.3.7 in the pom.xml file.	samples/client/others/java/webclient-useAbstractionForFiles/pom.xml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
maven/org.springframework.boot/[email protected] 🔁 maven/org.springframework.boot/[email protected]	Transitive: eval, filesystem, network, unsafe	+4	2.59 MB

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	maven/org.springframework.boot/[email protected]	CVE: GHSA-36p3-wjmg-h94x Remote Code Execution in Spring Framework (CRITICAL) Affected versions: < 5.2.20.RELEASE Patched version: 5.2.20.RELEASE	samples/client/others/java/webclient-useAbstractionForFiles/pom.xml samples/client/petstore/java/webclient-jakarta/pom.xml samples/client/petstore/java/webclient-nullable-arrays/pom.xml samples/client/petstore/java/webclient-swagger2/pom.xml samples/client/petstore/java/webclient/pom.xml	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore maven/org.springframework.boot/[email protected]