# CVE-2018-17082: Cross-site scripting in n/a

> An attacker can execute arbitrary scripts in the victim's browser via a crafted chunked request in PHP's Apache2 handler.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-17082, DLA-1509-1, GHSA-rhx7-v569-mfc2, SUSE-SU-2018:2887-1, SUSE-SU-2018:3016-1, SUSE-SU-2018:3017-1, SUSE-SU-2018:3018-1, UBUNTU-CVE-2018-17082

## What is CVE-2018-17082?

CVE-2018-17082 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 16 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Apache2 component in PHP before 5.6.38, 7.0.x before 7.0.32, 7.1.x before 7.1.22, and 7.2.x before 7.2.10 allows XSS via the body of a "Transfer-Encoding: chunked" request, because the bucket brigade is mishandled in the php_handler function in sapi/apache2handler/sapi_apache2.c.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-17082?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php5` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 5.5.14-109.41.1 |
| `php7` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 7.0.7-50.52.1 |
| `php7` | SUSE:Linux Enterprise Module for Web and Scripting 15 | All versions | 7.2.5-4.12.2 |
| `php53` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 5.3.17-112.41.1 |
| `php53` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 5.3.17-112.41.1 |
| `php53` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 5.3.17-112.41.1 |
| `php5` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 5.5.14-109.41.1 |
| `php7` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 7.0.7-50.52.1 |

Products: Debian Debian Linux, Netapp Storage Automation Store, Php Php.

## How do I fix CVE-2018-17082?

Upgrade to a fixed version.

## Is CVE-2018-17082 being exploited?

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

Public exploit code:

- Apache2 - Transfer-Encoding Chunked XSS (nuclei): http/cves/2018/CVE-2018-17082.yaml

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17082 and fix it if it is affected.

What it is: CVE-2018-17082 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 16 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17082 exists.

Affected product: Debian Debian Linux. 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-2018-17082/ (Markdown: https://insights.sbomify.com/CVE-2018-17082/index.md)
```

## Sources

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

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