dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2023-34053

HIGH · 7.5 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to 6.0.14 or later.
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.0 - 6.0.13, 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 * io.micrometer:micrometer-core is on the classpath * an ObservationRegistry is configured in the application to record observations Typically, Spring Boot applications need the org.springframework.boot:spring-boot-actuator dependency 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 · high confidence

A denial-of-service vulnerability in Spring Framework versions 6.0.0-6.0.13 allows specially crafted HTTP requests to cause DoS when Spring MVC/WebFlux is used with micrometer-core on the classpath and an ObservationRegistry is configured to record observations.

MitigationUpgrade Spring Framework to version 6.0.14 or later, or remove/disable the ObservationRegistry configuration if upgrade is not immediately feasible.

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.0, < 6.0.14

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. Determine Spring Framework version
    Check your project dependencies (pom.xml, build.gradle, or the spring-core JAR manifest) to identify the exact Spring Framework version in use
    Affected if The version is 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, or 6.0.13
  2. Verify micrometer-core dependency
    Inspect your project dependencies to determine if micrometer-core library is present on the classpath (check pom.xml, build.gradle, or packaged JARs)
    Affected if micrometer-core is included as a dependency
  3. Confirm Spring MVC or WebFlux usage
    Check your project for spring-webmvc or spring-webflux dependencies, or verify that controllers annotated with @RestController/@Controller or @RestControllerAdvice are present
    Affected if Spring MVC or Spring WebFlux is being used in the application
  4. Check ObservationRegistry configuration
    Search configuration files and Java code for any bean definitions of type ObservationRegistry, or properties/beans that configure observation recording (such as ObservationRegistry.observationConfig() or micrometer.observation.enabled=true)
    Affected if An ObservationRegistry bean exists and is configured to record observations (not disabled)

The environment is affected if Spring Framework version is 6.0.0 through 6.0.13 AND micrometer-core is on the classpath AND Spring MVC/WebFlux is used AND an ObservationRegistry is configured to record observations.

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 6.0.14 or later
Fixed in 6.0.14
Interim mitigation

Upgrade Spring Framework to version 6.0.14 or later, or remove/disable the ObservationRegistry configuration if upgrade is not immediately feasible.

Recommended fix High confidence

Spring Framework 6.0.14

  1. Upgrade Spring Framework from any version >= 6.0.0 and < 6.0.14 to version 6.0.14 or later
  2. If using Maven, update the spring-framework-bom and spring-core dependencies to version 6.0.14 or later
  3. If using Gradle, update the org.springframework dependency group to version 6.0.14 or later
  4. Rebuild and redeploy the application
Caveat Minor version upgrade within 6.x - review release notes for any deprecated APIs or behavioral changes

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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