# CVE-2017-11502: Path traversal in n/a

> Remote attackers can read arbitrary files on Technicolor DOCSIS devices via path traversal on port 4321.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/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:** No
- **Published:** 20 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6hpv-wh5x-v2wc

## What is CVE-2017-11502?

CVE-2017-11502 is a critical path traversal vulnerability in n/a, published on 20 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Technicolor DPC3928AD DOCSIS devices allow remote attackers to read arbitrary files via a request starting with "GET /../" on TCP port 4321.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Dpc3928ad Docsis Wireless Router Firmware.

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

No fix has been published for CVE-2017-11502 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11502 being exploited?

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

Public exploit code:

- Cisco DPC3928 Router - Arbitrary File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11502 is a critical path traversal vulnerability in n/a, published on 20 Jul 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-11502 in the wild and no public exploit code.

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

## Sources

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

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