dbcve.org
Spring BootFramework / library · VMware

CVE-2023-34055

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to after 3.1.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Boot versions 2.7.0 - 2.7.17, 3.0.0-3.0.12 and 3.1.0-3.1.5, 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 or Spring WebFlux * org.springframework.boot:spring-boot-actuator is on the classpath

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 in Spring Boot's actuator endpoints. When Spring MVC or Spring WebFlux is used together with spring-boot-actuator on the classpath, specially crafted HTTP requests can trigger a DoS condition.

MitigationUpgrade Spring Boot to version 2.7.18+, 3.0.13+, or 3.1.6+ to patch this vulnerability.

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 BootFramework / library
Affected:>= 2.7.0, <= 2.7.17>= 3.0.0, <= 3.0.12>= 3.1.0, <= 3.1.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify spring-boot-actuator is on the classpath
    Inspect your project dependencies (Maven pom.xml, Gradle build.gradle, or the lib/ directory of the deployed application) for the spring-boot-actuator artifact.
    Affected if spring-boot-actuator is present in the dependencies
  2. Confirm Spring MVC or Spring WebFlux is in use
    Check dependencies for spring-boot-starter-web (Spring MVC) or spring-boot-starter-webflux (Spring WebFlux), or verify the application uses annotations like @RestController or @Controller.
    Affected if Either Spring MVC or Spring WebFlux is included alongside actuator
  3. Determine the Spring Boot version
    Check the spring-boot.version property in pom.xml, the build.gradle file, or the MANIFEST.MF file in the deployed spring-boot JAR (the Spring-Boot-Version attribute).
    Affected if The version falls within 2.7.0-2.7.17, 3.0.0-3.0.12, or 3.1.0-3.1.5
  4. Check if actuator endpoints are exposed
    Inspect application.properties or application.yml for management.endpoints.web.exposure.include or management.endpoints.exposure.include settings. If not set, default endpoints may still be accessible.
    Affected if Any actuator endpoints are exposed via HTTP (especially /health, /metrics, or env)

You are affected if spring-boot-actuator and Spring MVC/WebFlux are on the classpath, your Spring Boot version is in the affected ranges, and actuator endpoints are HTTP-accessible.

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
Upgrade available Upgrade to a release after 3.1.5
Interim mitigation

Upgrade Spring Boot to version 2.7.18+, 3.0.13+, or 3.1.6+ to patch this vulnerability.

Recommended fix High confidence

Upgrade to Spring Boot 2.7.18+ (if on 2.7.x), 3.0.13+ (if on 3.0.x), or 3.1.6+ (if on 3.1.x)

  1. Identify the current Spring Boot version in use (check pom.xml or build.gradle)
  2. For 2.7.x branch: upgrade spring-boot version to 2.7.18 or later in pom.xml/build.gradle
  3. For 3.0.x branch: upgrade spring-boot version to 3.0.13 or later in pom.xml/build.gradle
  4. For 3.1.x branch: upgrade spring-boot version to 3.1.6 or later in pom.xml/build.gradle
  5. Run mvn clean install or ./gradlew build to rebuild the application
  6. Deploy the rebuilt application
  7. Verify the application starts successfully and test key functionality
Caveat Patch releases within the same minor version typically have no breaking changes; however, validate application functionality after upgrade

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

Fix this in Spring Boot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34055 — 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-2023-34055 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