[Snyk] Fix for 2 vulnerabilities

[ekmixon]

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

Snyk changed the following file(s):

• archived/v0.22-docs/serving/samples/cloudevents/cloudevents-spring/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Denial of Service (DoS) SNYK-JAVA-ORGSPRINGFRAMEWORK-8384234	631	Major version upgrade No Known Exploit
	Improper Handling of Case Sensitivity SNYK-JAVA-ORGSPRINGFRAMEWORK-8230365	329	org.springframework.cloud:spring-cloud-function-web: 3.1.0-M5 -> 4.1.4 No Known Exploit

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade org.springframework.boot:[email protected] to org.springframework.boot:[email protected]; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/boot/spring-boot-dependencies/2.4.0/spring-boot-dependencies-2.4.0.pom

---

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:

🦉 Denial of Service (DoS)

Summary by Sourcery

Bug Fixes:

• Upgrade org.springframework.cloud:spring-cloud-function-web from version 3.1.0-M5 to 4.1.4 to address vulnerabilities including Denial of Service (DoS) and Improper Handling of Case Sensitivity.

[secure-code-warrior-for-github]

Micro-Learning Topic: Denial of service (Detected by phrase)

Matched on "Denial of Service"

The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others. Source: https://www.owasp.org/index.php/Denial_of_Service

Try a challenge in Secure Code Warrior

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR addresses security vulnerabilities by upgrading Spring Cloud Function Web dependency. The changes are implemented through version updates in the Maven POM file to fix two identified vulnerabilities: a medium-severity Denial of Service (DoS) issue and a low-severity case sensitivity handling problem.

ER Diagram for Maven Dependency Changes

erDiagram
    POM {
        string groupId
        string artifactId
        string version
    }

    POM ||--o{ Dependency : contains
    Dependency {
        string groupId
        string artifactId
        string version
    }

    Dependency }|..|{ SpringCloudFunctionWeb : is
    SpringCloudFunctionWeb {
        string version
    }

    Dependency }|..|{ SpringBootStarterWeb : is
    SpringBootStarterWeb {
        string version
    }

    POM }|..|{ Parent : extends
    Parent {
        string groupId
        string artifactId
        string version
    }

    note for SpringCloudFunctionWeb "Upgraded from 3.1.0-M5 to 4.1.4 to fix vulnerabilities"
    note for SpringBootStarterWeb "Upgrade to 3.0.0 not applied due to external management"

Loading

File-Level Changes

Change	Details	Files
Upgrade Spring Cloud Function Web dependency to address security vulnerabilities	Update spring-cloud-function-web version from 3.1.0-M5 to 4.1.4 Fix medium severity DoS vulnerability (SNYK-JAVA-ORGSPRINGFRAMEWORK-8384234) Fix low severity case sensitivity handling vulnerability (SNYK-JAVA-ORGSPRINGFRAMEWORK-8230365)	archived/v0.22-docs/serving/samples/cloudevents/cloudevents-spring/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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.