How severe is CVE-2023-34055?

CVE-2023-34055 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-34055?

CVE-2023-34055 affects the following packages: org.springframework.boot:spring-boot-actuator (Maven), org.springframework.boot:spring-boot-actuator (Maven), org.springframework.boot:spring-boot-actuator (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-34055?

Update org.springframework.boot:spring-boot-actuator to 2.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34055 is resolved across your whole dependency graph.

How do I detect CVE-2023-34055 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-actuator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2023-34055 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2023-34055?

O3 pinpoints whether CVE-2023-34055 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2023-34055 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-34055 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2023-34055 published, and has it been updated?

CVE-2023-34055 was published on November 28, 2023 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2023-34055

MEDIUM

CVE-2023-34055 is a medium-severity (CVSS 5.3) vulnerability in org.springframework.boot:spring-boot-actuator. O3 Security confirms whether CVE-2023-34055 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring Boot server Web Observations DoS Vulnerability

Also known asGHSA-jjfh-589g-3hjx

Published

Nov 28, 2023

Updated

Jul 15, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕org.springframework.boot:spring-boot-actuator☕org.springframework.boot:spring-boot-actuator☕org.springframework.boot:spring-boot-actuator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.boot:spring-boot-actuator`	all versions	2.7.18
☕Maven	`org.springframework.boot:spring-boot-actuator`	≥ 3.0.0&&< 3.0.13	3.0.13
☕Maven	`org.springframework.boot:spring-boot-actuator`	≥ 3.1.0&&< 3.1.6	3.1.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-actuator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.boot:spring-boot-actuator to 2.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34055 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-34055 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-34055. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2023-34055 in your dependencies?

O3 detects CVE-2023-34055 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works