Denial of Service Vulnerability in libspring-java

libspring-java Updated 02 Oct 2025

Summary

12/05/2022
N/A
No i
Medium
6.5

CVE-2022-22971: In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user. Affects libspring-java across 2 version ranges.

>= 5acffaa72da10ba42fe547eeea44d8615cbf99b9, <= cedb5874b72c3311c8c6e2f03a53537590f2e0dc >= 927b8c15ef20eaaa4002d4b2170cc536a6d6aa35, <= 2bdab894f159e54d833c5850c81a55a0596e7b14

No fix is published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libspring-java is a Java library that provides the Spring Framework, which is a popular open-source application framework for building Java applications. It offers a comprehensive programming and configuration model for modern Java-based enterprise applications. However, versions prior to 5.3.20+, 5.2.22+, and old unsupported versions of libspring-java are vulnerable to a denial of service attack when using a STOMP over WebSocket endpoint. This vulnerability can be exploited by an authenticated user.

Vulnerability Detail

The vulnerability (CVE-2022-22971) in libspring-java allows an authenticated user to launch a denial of service attack. By exploiting a weakness in the STOMP over WebSocket endpoint, an attacker can overload the application and cause it to become unresponsive or crash. This can lead to service disruption and potential financial losses for organizations relying on applications built with libspring-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is currently no known workaround for this vulnerability. It is essential to upgrade to the patched versions of libspring-java to address the issue effectively.

Conclusion

The denial of service vulnerability in libspring-java can be mitigated by upgrading to the latest patched versions. It is crucial for organizations using libspring-java to promptly apply the necessary updates to ensure the security and stability of their applications. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

libspring-java is a Java library that provides the Spring Framework, an open-source application framework for building Java applications.

The vulnerability allows an authenticated user to launch a denial of service attack, potentially causing service disruption and financial losses.

Versions prior to 5.3.20+, 5.2.22+, and old unsupported versions of libspring-java are vulnerable to this denial of service vulnerability.

To fix this vulnerability, upgrade to the latest version of libspring-java (5.3.20+ or 5.2.22+).

No, there is currently no known workaround for this vulnerability. Upgrading to the patched versions is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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