# CVE-2023-34062: In Reactor Netty HTTP Server a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack

> Attackers can read arbitrary files via directory traversal in Reactor Netty when static resources are served.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Nov 2023
- **Updated:** 29 Aug 2024
- **Also known as:** CLSA-2026-1776126825, GHSA-xjhv-p3fv-x24r, ROOT-APP-MAVEN-CVE-2023-34062

## What is CVE-2023-34062?

CVE-2023-34062 is a high-severity path traversal vulnerability in Reactor Netty, published on 15 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack.

Specifically, an application is vulnerable if Reactor Netty HTTP Server is configured to serve static resources.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-34062?

4 open source packages ship an affected version, including io.projectreactor.netty:reactor-netty-http. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.0.0 | 1.0.39 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.0.0 | 1.0.39 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.1.0 | 1.1.13 |
| `io.projectreactor.netty:reactor-netty-http` | Maven | From 1.1.0 | 1.1.13 |

Products: Broadcom Reactor Netty.

## How do I fix CVE-2023-34062?

Upgrade io.projectreactor.netty:reactor-netty-http to a fixed version for your release line: 1.0.39 or 1.1.13.

## Is CVE-2023-34062 being exploited?

There is no known exploitation of CVE-2023-34062 in the wild and no public exploit code.

## Other vulnerabilities in Reactor Netty

- [CVE-2019-11284](https://insights.sbomify.com/CVE-2019-11284/): Reactor Netty authentication leak in redirects (medium 6.8)
- [CVE-2020-5403](https://insights.sbomify.com/CVE-2020-5403/): DoS Via Malformed URL with Reactor Netty HTTP Server (medium 6.5)
- [CVE-2020-5404](https://insights.sbomify.com/CVE-2020-5404/): Authentication Leak On Redirect With Reactor Netty HttpClient (medium 6.5)
- [CVE-2026-47848](https://insights.sbomify.com/CVE-2026-47848/): Reactor Netty WebSocket Client Leaks Credentials On Redirect (medium 6.1)
- [CVE-2026-47844](https://insights.sbomify.com/CVE-2026-47844/): Reactor Netty HTTP Server Leaks Exception Details (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34062 and fix it if it is affected.

What it is: CVE-2023-34062 is a high-severity path traversal vulnerability in Reactor Netty, published on 15 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34062 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.0.0; fixed in 1.0.39
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.0.0; fixed in 1.0.39
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.1.0; fixed in 1.1.13
- io.projectreactor.netty:reactor-netty-http (Maven): affected from 1.1.0; fixed in 1.1.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-34062/ (Markdown: https://insights.sbomify.com/CVE-2023-34062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34062
- OSV: https://osv.dev/vulnerability/CVE-2023-34062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34062/
Summaries are generated and may contain mistakes; the official description above is the record.