dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2024-22233

HIGH · 7.5 CVSS v3.1 Published 2024-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

A denial-of-service vulnerability exists in Spring Framework 6.0.15 and 6.1.2 where specially crafted HTTP requests can cause DoS conditions in applications using Spring MVC combined with Spring Security 6.1.6+ or 6.2.1+. The vulnerability is triggered through the Spring MVC request processing path when Spring Security is present.

MitigationUpgrade Spring Framework to versions newer than 6.0.15 and 6.1.2 (refer to official Spring advisories for fixed versions), and ensure Spring Security is also updated to a compatible patched version.

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 FrameworkFramework / library
Affected:= 6.0.15= 6.1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Spring Framework version
    Inspect your project's dependency management file (pom.xml, build.gradle) or list the spring-core-* JAR files in your classpath to find the exact Spring Framework version. Check for spring-core, spring-web, or other Spring Framework module versions.
    Affected if The version is exactly 6.0.15 or 6.1.2
  2. Confirm Spring MVC is in use
    Verify your application uses Spring MVC by checking for @Controller or @RestController annotated classes, or presence of spring-web JAR in your dependencies, or Spring MVC related configuration in your application.
    Affected if Spring MVC is enabled and handling HTTP requests
  3. Identify installed Spring Security version
    Inspect your dependency management file (pom.xml, build.gradle) or list the spring-security-* JAR files in your classpath to determine the exact Spring Security version.
    Affected if Spring Security version is 6.1.6 or higher, or 6.2.1 or higher

You are affected if your environment uses Spring Framework exactly version 6.0.15 or 6.1.2, has Spring MVC enabled for request processing, and includes Spring Security version 6.1.6+ or 6.2.1+.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Framework to versions newer than 6.0.15 and 6.1.2 (refer to official Spring advisories for fixed versions), and ensure Spring Security is also updated to a compatible patched version.

Recommended fix High confidence

Spring Framework 6.0.16 or later (6.1.x users: upgrade to 6.1.3 or later)

  1. 1. Locate the pom.xml or build.gradle file for your Spring Boot application
  2. 2. Find the Spring Framework version managed by spring-boot-starter-parent or explicitly defined
  3. 3. For Maven: Update the spring-framework-bom or spring-boot-starter-web version to 6.0.16 or later
  4. 4. For Gradle: Update the springBoot plugin or dependency management to resolve Spring Framework 6.0.16+ or 6.1.3+
  5. 5. Run mvn clean install or ./gradlew build to apply the update
  6. 6. Run your application's test suite to verify functionality is intact
  7. 7. Deploy the updated application
Caveat Minor patch update; likely no breaking changes, but regression testing is recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22233 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22233 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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