# CVE-2023-38522: Apache Traffic Server: Incomplete field name check allows request smuggling

> Attackers can smuggle requests or poison caches by exploiting incomplete HTTP field name validation in Apache Traffic Server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 26 Jul 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-38522, GHSA-68qf-xhq3-9qj5, UBUNTU-CVE-2023-38522

## What is CVE-2023-38522?

CVE-2023-38522 is a high-severity vulnerability in Apache Traffic Server, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Traffic Server accepts characters that are not allowed for HTTP field names and forwards malformed requests to origin servers. This can be utilized for request smuggling and may also lead cache poisoning if the origin servers are vulnerable.

This issue affects Apache Traffic Server: from 8.0.0 through 8.1.10, from 9.0.0 through 9.2.4.

Users are recommended to upgrade to version 8.1.11 or 9.2.5, which fixes the issue.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 1 product.


Products: Apache Traffic Server.

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

Upgrade to a fixed version.

## Is CVE-2023-38522 being exploited?

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

## Other vulnerabilities in Apache Traffic Server

- [CVE-2014-3525](https://insights.sbomify.com/CVE-2014-3525/): Other in n/a (critical 10.0)
- [CVE-2021-43082](https://insights.sbomify.com/CVE-2021-43082/): heap-buffer-overflow with stats-over-http plugin (critical 9.8)
- [CVE-2021-35474](https://insights.sbomify.com/CVE-2021-35474/): Dynamic stack buffer overflow in cachekey plugin (critical 9.8)
- [CVE-2019-17559](https://insights.sbomify.com/CVE-2019-17559/): Other in Apache Traffic Server (critical 9.8)
- [CVE-2019-17565](https://insights.sbomify.com/CVE-2019-17565/): Other in Apache Traffic Server (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38522 is a high-severity vulnerability in Apache Traffic Server, published on 26 Jul 2024. 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-38522 in the wild and no public exploit code.

Affected product: Apache Traffic Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-38522/ (Markdown: https://insights.sbomify.com/CVE-2023-38522/index.md)
```

## Sources

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

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