CVE-2017-18368
Zyxel P660HN-T1A Routers Command Injection Vulnerability
Zyxel P660HN-T1A Routers
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 7 August 2023. US federal agencies were required to remediate it by 28 August 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 94.5%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2017-18368 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-18368.
What does CVE-2017-18368 affect?
CVE-2017-18368 affects Zyxel P660HN-T1A Routers. 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.
How severe is CVE-2017-18368?
CVE-2017-18368 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 94.5%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 28 August 2023.
How should organisations respond to CVE-2017-18368?
Apply the vendor patch for Zyxel P660HN-T1A Routers as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.