dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-22271

HIGH · 8.2 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Spring Cloud Function framework, versions 4.1.x prior to 4.1.2, 4.0.x prior to 4.0.8 an application is vulnerable to a DOS attack when attempting to compose functions with non-existing functions. Specifically, an application is vulnerable when all of the following are true: User is using Spring Cloud Function Web module Affected Spring Products and Versions Spring Cloud Function Framework 4.1.0 to 4.1.2 4.0.0 to 4.0.8 References https://spring.io/security/cve-2022-22979   https://checkmarx.com/blog/spring-function-cloud-dos-cve-2022-22979-and-unintended-function-invocation/  History 2020-01-16: Initial vulnerability report published.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Cloud Function versions 4.1.x prior to 4.1.2 and 4.0.x prior to 4.0.8 contain a Denial of Service vulnerability triggered when attempting to compose functions with non-existing function names. The vulnerability requires the Spring Cloud Function Web module to be in use, and causes the application to fail or become unresponsive when invalid function references are used in composition attempts.

MitigationUpgrade Spring Cloud Function to version 4.1.2 or 4.0.8 or later which contains the fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Cloud Function dependency
    Examine your project's build file (pom.xml or build.gradle) for the spring-cloud-function-core or spring-cloud-function-web dependency and note its version.
    Affected if The dependency is present with a version between 4.0.0 and 4.0.7, or between 4.1.0 and 4.1.1.
  2. Verify Spring Cloud Function Web module is enabled
    Check if spring-cloud-function-web is listed as a dependency in your build configuration, or look for the org.springframework.cloud.function.web package being used in your application.
    Affected if The spring-cloud-function-web module is present in the classpath.
  3. Confirm function composition configuration
    Review application.properties or application.yml for spring.cloud.function.composition or similar composition-related properties, or inspect any Java code that uses FunctionComposition or similar APIs.
    Affected if Function composition is configured or the application accepts user-provided function names for composition.
  4. Check installed Spring Cloud Function version
    Run a dependency tree command (mvn dependency:tree or ./gradlew dependencies) and search for spring-cloud-function-core or spring-cloud-function-web to verify the exact version.
    Affected if The version resolves to 4.0.x prior to 4.0.8 or 4.1.x prior to 4.1.2.

You are affected if Spring Cloud Function Web module is in use, the version is 4.0.x < 4.0.8 or 4.1.x < 4.1.2, and function composition with potentially invalid function names is possible in your application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Cloud Function to version 4.1.2 or 4.0.8 or later which contains the fix for this vulnerability.

Recommended fix High confidence

Spring Cloud Function 4.0.8 or 4.1.2

  1. Identify your current Spring Cloud Function version in your Maven pom.xml or Gradle build file
  2. For Spring Cloud Function 4.0.x users: upgrade spring-cloud-function-core dependency to version 4.0.8 or later
  3. For Spring Cloud Function 4.1.x users: upgrade spring-cloud-function-core dependency to version 4.1.2 or later
  4. Update the dependency management and resolve dependencies
  5. Verify the upgrade was applied correctly by checking the resolved library version
  6. Test the application to confirm function composition works and the DOS vulnerability is mitigated
Caveat Minor version upgrades may include behavioral changes; review Spring Cloud Function release notes for any breaking changes between your version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22271 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22271 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data