# CVE-2017-7668: Memory corruption in Apache HTTP Server

> A bug in Apache HTTP Server's token parsing allows attackers to cause segmentation faults or incorrect values via crafted headers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-7668, CLEANSTART-2026-TI49446, DEBIAN-CVE-2017-7668, GHSA-mcc7-rcr3-2rgr, UBUNTU-CVE-2017-7668

## What is CVE-2017-7668?

CVE-2017-7668 is a high-severity memory corruption vulnerability in Apache Http Server, published on 20 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows ap_find_token() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to force ap_find_token() to return an incorrect value.

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2017-7668?

It affects 13 products.


Products: Apache Http Server, Apple Mac Os X, Debian Debian Linux, Netapp Clustered Data Ontap, Netapp Oncommand Unified Manager, Netapp Storagegrid, Oracle Secure Global Desktop, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2017-7668?

Upgrade to a fixed version.

## Is CVE-2017-7668 being exploited?

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

## Other vulnerabilities in Apache Http Server

- [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild)
- [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild)
- [CVE-2019-0211](https://insights.sbomify.com/CVE-2019-0211/): Apache HTTP Server Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7668 and fix it if it is affected.

What it is: CVE-2017-7668 is a high-severity memory corruption vulnerability in Apache Http Server, published on 20 Jun 2017. 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-2017-7668 in the wild and no public exploit code.

Affected product: Apache Http 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-2017-7668/ (Markdown: https://insights.sbomify.com/CVE-2017-7668/index.md)
```

## Sources

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

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