CVE-2022-22971: Allocation of Resources Without Limits or Throttling in Spring Framework
Summary
CVE-2022-22971: Allocation of Resources Without Limits or Throttling in Spring Framework. Affects org.springframework:spring-messaging across 2 version ranges.
< 5.2.22.RELEASE
>= 5.3.0, < 5.3.20
Fixed in 5.2.22.RELEASE or 5.3.20, depending on the release line you run. How to fix ↓
Also tracked for
- libspring-java · Debian:11
The same CVE-2022-22971 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
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.
No signup required · Results in about 60 seconds
Background
The Spring Framework is a popular open-source application framework for Java. It provides comprehensive infrastructure support for developing Java applications. The 'org.springframework:spring-core' package is a core component of the Spring Framework, providing essential functionality for dependency injection, resource management, and other key features. However, versions prior to 5.3.20+, 5.2.22+, and old unsupported versions are vulnerable to a denial of service attack when using a STOMP over WebSocket endpoint.
Vulnerability Detail
The vulnerability allows an authenticated user to launch a denial of service attack against an application using the Spring Framework. By exploiting the vulnerability, an attacker can allocate excessive resources without any limits or throttling, leading to a significant degradation in application performance or even a complete outage. This vulnerability can be particularly damaging in production environments where multiple users are concurrently accessing the application.
How To Fix
Latest published version: 7.1.0-RC1 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 5.2.22.RELEASE5.2.22.RELEASE -
>= 5.3.0, < 5.3.205.3.20
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, developers can disable the STOMP over WebSocket endpoint if it is not essential for the application's functionality. This can be achieved by modifying the application's configuration or removing the relevant code. However, this workaround may impact the application's functionality and should only be considered if the endpoint is not actively used.
Conclusion
The vulnerability in the Spring Framework allows an authenticated user to launch a denial of service attack, potentially causing significant harm to the affected application. It is crucial to upgrade to the latest patched versions of the Spring Framework (5.3.20+ or 5.2.22+) to mitigate this vulnerability. Regularly updating all dependencies is also important to ensure the application is protected against the latest security threats. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for org.springframework:spring-messaging →
FAQ
The vulnerability allows an authenticated user to launch a denial of service attack, potentially causing a significant degradation in application performance or even a complete outage.
Versions prior to 5.3.20+, 5.2.22+, and old unsupported versions are vulnerable to this denial of service attack.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your pom.xml file and Vulert will analyze it for any open-source vulnerabilities, including this specific vulnerability.
At the time of this report, there are no known public exploits for this vulnerability. However, it is important to patch your application as soon as possible to prevent any potential attacks.
As a temporary workaround, you can disable the STOMP over WebSocket endpoint if it is not essential for your application's functionality. However, this may impact the application's functionality and should only be considered if the endpoint is not actively used.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.springframework:spring-messaging.
