# CVE-2017-18368: Zyxel P660HN-T1A Routers Command Injection

> Unauthenticated attackers can execute arbitrary commands via the remote_host parameter in the ViewLog.asp page of ZyXEL P660HN-T1A routers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Aug 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-8hjr-66w2-mg84

## What is CVE-2017-18368?

CVE-2017-18368 is a critical command injection vulnerability in n/a, published on 2 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ZyXEL P660HN-T1A v1 TCLinux Fw $7.3.15.0 v001 / 3.40(ULM.0)b31 router distributed by TrueOnline has a command injection vulnerability in the Remote System Log forwarding function, which is accessible by an unauthenticated user. The vulnerability is in the ViewLog.asp page and can be exploited through the remote_host parameter.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 3 products.


Products: Billion 5200w-T Firmware, Zyxel P660hn-T1a V1 Firmware, Zyxel P660hn-T1a V2 Firmware.

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

No fix has been published for CVE-2017-18368 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Aug 2023.

## Is CVE-2017-18368 being exploited?

Yes. Attackers have exploited CVE-2017-18368 in the wild since at least 7 Aug 2023.

Public exploit code:

- TrueOnline / ZyXEL P660HN-T v1 Router Unauthenticated Command Injection (metasploit)

## Other vulnerabilities in n/a

- [CVE-2017-18369](https://insights.sbomify.com/CVE-2017-18369/): Command injection in n/a (critical 9.8)
- [CVE-2017-18371](https://insights.sbomify.com/CVE-2017-18371/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-18370](https://insights.sbomify.com/CVE-2017-18370/): Command injection in n/a (high 8.8)
- [CVE-2017-18372](https://insights.sbomify.com/CVE-2017-18372/): Command injection in n/a (high 8.8)
- [CVE-2017-18373](https://insights.sbomify.com/CVE-2017-18373/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18368 is a critical command injection vulnerability in n/a, published on 2 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-18368 in the wild since at least 7 Aug 2023.

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

## Sources

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

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