Spring Cloud FunctionFramework / library · VMware
CVE-2022-22979
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 · uneditedIn Spring Cloud Function versions prior to 3.2.6, it is possible for a user who directly interacts with framework provided lookup functionality to cause a denial-of-service condition due to the caching issue in the Function Catalog component of the framework.
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 confidenceA denial-of-service vulnerability exists in Spring Cloud Function's Function Catalog component where the caching mechanism can be exploited via the lookup functionality. A user directly interacting with this functionality can trigger excessive caching, leading to resource exhaustion and service unavailability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring Cloud FunctionFramework / library
< 3.2.6CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Cloud Function installationCheck project dependencies (Maven pom.xml, Gradle build.gradle) or application classpath for 'spring-cloud-function' jar presenceAffected if Spring Cloud Function dependency is present in the project
-
Determine installed Spring Cloud Function versionReview the resolved version of spring-cloud-function in build artifacts, dependency tree (mvn dependency:tree or gradle dependencies), or check the jar manifestAffected if Version is lower than 3.2.6 (e.g., 3.2.5, 3.2.0, etc.)
-
Check if function routing/lookup is enabledInspect application.properties or application.yml for 'spring.cloud.function.definition' or 'spring.cloud.function.routing.enabled' configuration propertiesAffected if Function routing or lookup via FunctionCatalog is explicitly defined or auto-configured
-
Verify caching configuration for function lookupSearch configuration files for caching-related properties affecting FunctionCatalog, such as spring.cloud.function.caching or custom cache settingsAffected if Caching is enabled for function lookup operations (default behavior exposes the vulnerability)
-
Confirm exposure of lookup endpointReview if the application exposes HTTP endpoints that route to function lookup (via spring.cloud.function.web.routing.enabled or similar)Affected if HTTP routing to functions is enabled, allowing direct interaction with the lookup functionality
The environment is affected if Spring Cloud Function version is below 3.2.6 AND the function routing/lookup feature is enabled, allowing attackers to trigger excessive caching through the FunctionCatalog component.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.6
Upgrade Spring Cloud Function to version 3.2.6 or later to resolve the caching issue in the Function Catalog component.
Spring Cloud Function 3.2.6
- 1. Identify the current Spring Cloud Function version in use by checking project dependencies (e.g., pom.xml, build.gradle)
- 2. Update the Spring Cloud Function dependency to version 3.2.6 or later
- 3. For Maven projects, update the dependency in pom.xml: change version to 3.2.6
- 4. For Gradle projects, update the dependency in build.gradle: change version to '3.2.6'
- 5. Rebuild and test the application to ensure functionality remains intact
- 6. Deploy the updated application to production environments
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Cloud Function
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22979 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22979 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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