# CVE-2017-15637: Command injection in n/a

> Remote authenticated administrators can execute arbitrary commands on TP-Link WVR, WAR, and ER devices via a command injection vulnerability.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-43q2-3hxx-r5j2

## What is CVE-2017-15637?

CVE-2017-15637 is a high-severity command injection vulnerability in n/a, published on 11 Jan 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

TP-Link WVR, WAR and ER devices allow remote authenticated administrators to execute arbitrary commands via command injection in the pptphellointerval variable in the pptp_server.lua file.

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

It affects 38 products.


Products: Tp-Link Er5110g Firmware, Tp-Link Er5120g Firmware, Tp-Link Er5510g Firmware, Tp-Link Er5520g Firmware, Tp-Link R4149g Firmware, Tp-Link R4239g Firmware, Tp-Link R4299g Firmware, Tp-Link R473 Firmware, Tp-Link R473g Firmware, Tp-Link R473gp-Ac Firmware, Tp-Link R473p-Ac Firmware, Tp-Link R478\+ Firmware, Tp-Link R478 Firmware, Tp-Link R478g\+ Firmware, Tp-Link R483 Firmware, Tp-Link R483g Firmware, Tp-Link R488 Firmware, Tp-Link War1300l Firmware, Tp-Link War1750l Firmware, Tp-Link War2600l Firmware and 18 more.

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

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

## Is CVE-2017-15637 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15613](https://insights.sbomify.com/CVE-2017-15613/): Command injection in n/a (high 7.2)
- [CVE-2017-15614](https://insights.sbomify.com/CVE-2017-15614/): Command injection in n/a (high 7.2)
- [CVE-2017-15615](https://insights.sbomify.com/CVE-2017-15615/): Command injection in n/a (high 7.2)
- [CVE-2017-15616](https://insights.sbomify.com/CVE-2017-15616/): Command injection in n/a (high 7.2)
- [CVE-2017-15617](https://insights.sbomify.com/CVE-2017-15617/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15637 is a high-severity command injection vulnerability in n/a, published on 11 Jan 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15637 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-15637/ (Markdown: https://insights.sbomify.com/CVE-2017-15637/index.md)
```

## Sources

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

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