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

> An out-of-bounds write in Apache HTTP Server's mod_authnz_ldap can cause a crash, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 26 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** ALPINE-CVE-2017-15710, CLEANSTART-2026-YA72410, DEBIAN-CVE-2017-15710, GHSA-9q97-qm54-9797, UBUNTU-CVE-2017-15710

## What is CVE-2017-15710?

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

### Official description

In Apache httpd 2.0.23 to 2.0.65, 2.2.0 to 2.2.34, and 2.4.0 to 2.4.29, mod_authnz_ldap, if configured with AuthLDAPCharsetConfig, uses the Accept-Language header value to lookup the right charset encoding when verifying the user's credentials. If the header value is not present in the charset conversion table, a fallback mechanism is used to truncate it to a two characters value to allow a quick retry (for example, 'en-US' is truncated to 'en'). A header value of less than two characters forces an out of bound write of one NUL byte to a memory location that is not part of the string. In the worst case, quite unlikely, the process would crash which could be used as a Denial of Service attack. In the more likely case, this memory is already reserved for future use and the issue has no effect at all.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 8 products.


Products: Apache Http Server, Canonical Ubuntu Linux, Debian Debian Linux, Netapp Clustered Data Ontap, Netapp Santricity Cloud Connector, Netapp Storage Automation Store, Netapp Storagegrid, Redhat Enterprise Linux.

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

Upgrade to a fixed version.

## Is CVE-2017-15710 being exploited?

There is no known exploitation of CVE-2017-15710 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-15710 and fix it if it is affected.

What it is: CVE-2017-15710 is a high-severity memory corruption vulnerability in Apache Http Server, published on 26 Mar 2018. 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-15710 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-15710/ (Markdown: https://insights.sbomify.com/CVE-2017-15710/index.md)
```

## Sources

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

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