# CVE-2017-15715: Security feature bypass in Apache HTTP Server

> Attackers can bypass file upload restrictions by exploiting regex matching flaws in Apache HTTP Server's FilesMatch directive.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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-15715, CLEANSTART-2026-PP80959, DEBIAN-CVE-2017-15715, GHSA-p3h3-wpw6-m7vf, UBUNTU-CVE-2017-15715

## What is CVE-2017-15715?

CVE-2017-15715 is a high-severity 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.4.0 to 2.4.29, the expression specified in <FilesMatch> could match '$' to a newline character in a malicious filename, rather than matching only the end of the filename. This could be exploited in environments where uploads of some files are are externally blocked, but only by matching the trailing portion of the filename.

Weakness: CWE-20 (Improper Input Validation)

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

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-15715?

Upgrade to a fixed version.

## Is CVE-2017-15715 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-15715 exists.

Public exploit code:

- https://github.com/whisp1830/CVE-2017-15715 (github_poc): https://github.com/whisp1830/CVE-2017-15715
- whs 4기 컨테이너 과제 (github_poc): https://github.com/ehsehs5652/CVE-2017-15715-httpd
- Vulhub httpd/CVE-2017-15715: Apache HTTP Server FilesMatch Newline Bypass (CVE-2017-15715), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-httpd-cve-2017-15715
- Apache httpd <=2.4.29 - Arbitrary File Upload (nuclei): http/cves/2017/CVE-2017-15715.yaml

## 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-15715 and fix it if it is affected.

What it is: CVE-2017-15715 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-15715 exists.

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

## Sources

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

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