CVE-2022-22979: Denial of Service in Spring Cloud Function

Summary

22/06/2022
Yes i
High
7.5

CVE-2022-22979: Denial of Service in Spring Cloud Function. Affects org.springframework.cloud:spring-cloud-function-parent versions < 3.2.6. Fixed in 3.2.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Spring Cloud Function is a framework that allows developers to write serverless functions using Spring Boot. It provides a catalog of functions that can be invoked by name or type. The Function Catalog component of the framework is responsible for caching and lookup of these functions. However, prior to version 3.2.6, there is a caching issue in the Function Catalog that can be exploited by a user interacting directly with the framework's lookup functionality.

Vulnerability Detail

The vulnerability in Spring Cloud Function allows an attacker to cause a denial-of-service (DoS) condition. By exploiting the caching issue in the Function Catalog, an attacker can overload the system by repeatedly invoking the lookup functionality. This can lead to resource exhaustion and impact the availability of the application. The vulnerability has a CVSS score of 7.5, indicating a high severity.

How To Fix

Latest published version: 5.1.0-RC1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.2.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to upgrade to the fixed version of Spring Cloud Function to mitigate the risk.

Conclusion

In conclusion, the vulnerability in Spring Cloud Function allows an attacker to cause a denial-of-service condition by exploiting a caching issue in the Function Catalog. To mitigate the risk, it is crucial to upgrade to the fixed version of Spring Cloud Function (3.2.6 or later). For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.springframework.cloud:spring-cloud-function-parent →

Share this vulnerability

FAQ

Spring Cloud Function is a framework that allows developers to write serverless functions using Spring Boot. It provides a catalog of functions that can be invoked by name or type.

The Function Catalog component of Spring Cloud Function is responsible for caching and lookup of the available functions in the catalog.

The vulnerability allows an attacker to cause a denial-of-service (DoS) condition, leading to resource exhaustion and impacting the availability of the application.

The CVSS score of this vulnerability is 7.5, indicating a high severity.

To fix this vulnerability, it is recommended to upgrade to Spring Cloud Function version 3.2.6 or later.

How To Fix

Latest published version: 5.1.0-RC1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.2.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback