Skip to content

Spring Framework server Web DoS Vulnerability

High severity GitHub Reviewed Published Jan 22, 2024 to the GitHub Advisory Database • Updated Feb 13, 2025

Package

maven org.springframework:spring-core (Maven)

Affected versions

= 6.1.2
= 6.0.15

Patched versions

6.1.3
6.0.16

Description

In Spring Framework versions 6.0.15 and 6.1.2, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition.

Specifically, an application is vulnerable when all of the following are true:

  • the application uses Spring MVC
  • Spring Security 6.1.6+ or 6.2.1+ is on the classpath

Typically, Spring Boot applications need the org.springframework.boot:spring-boot-starter-web and org.springframework.boot:spring-boot-starter-security dependencies to meet all conditions.

References

Published by the National Vulnerability Database Jan 22, 2024
Published to the GitHub Advisory Database Jan 22, 2024
Reviewed Jan 23, 2024
Last updated Feb 13, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(54th percentile)

Weaknesses

No CWEs

CVE ID

CVE-2024-22233

GHSA ID

GHSA-r4q3-7g4q-x89m

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.