title: ZyXEL NAS products running firmware version 5.21 and earlier are vulnerable to pre-authentication command injection in weblogin.cgi
description: Multiple ZyXEL network-attached storage (NAS) devices running firmware version 5.21 contain a pre-authentication command injection vulnerability, which may allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable device. ZyXEL NAS devices achieve authentication by using the weblogin.cgi CGI executable. This program fails to properly sanitize the username parameter that is passed to it. If the username parameter contains certain characters, it can allow command injection with the privileges of the web server that runs on the ZyXEL device. Although the web server does not run as the root user, ZyXEL devices include a setuid utility that can be leveraged to run any command with root privileges. As such, it should be assumed that exploitation of this vulnerability can lead to remote code execution with root privileges. By sending a specially-crafted HTTP POST or GET request to a vulnerable ZyXEL device, a remote, unauthenticated attacker may be able to execute arbitrary code on the device. This may happen by directly connecting to a device if it is directly exposed to an attacker. However, there are ways to trigger such crafted requests even if an attacker does not have direct connectivity to a vulnerable devices. For example, simply visiting a website can result in the compromise of any ZyXEL device that is reachable from the client system. Affected products include: NAS326 before firmware V5.21(AAZF.7)C0 NAS520 before firmware V5.21(AASZ.3)C0 NAS540 before firmware V5.21(AATB.4)C0 NAS542 before firmware V5.21(ABAG.4)C0 ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, and NAS542 devices. Affected models that are end-of-support: NSA210, NSA220, NSA220+, NSA221, NSA310, NSA310S, NSA320, NSA320S, NSA325 and NSA325v2
problem types: CWE-78 OS Command Injection
affected:
{
product: NAS326
vendor: ZyXEL
versions:
lessThanOrEqual: V5.21(AAZF.7)C0, status: affected, version: V5.21(AAZF.7)C0, versionType: custom
}
{
product: NAS520
vendor: ZyXEL
versions:
lessThanOrEqual: V5.21(AASZ.3)C0, status: affected, version: V5.21(AASZ.3)C0, versionType: custom
}
{
product: NAS540
vendor: ZyXEL
versions:
lessThanOrEqual: V5.21(AATB.4)C0, status: affected, version: V5.21(AATB.4)C0, versionType: custom
}
{
product: NAS542
vendor: ZyXEL
versions:
lessThanOrEqual: V5.21(ABAG.4)C0, status: affected, version: V5.21(ABAG.4)C0, versionType: custom
}
{
product: NSA210
vendor: ZyXEL
versions:
status: affected, version: all
}
{
product: NSA220
vendor: ZyXEL
versions:
status: affected, version: all
}
{
product: NSA220+
vendor: ZyXEL
versions:
status: affected, version: all
}
{
product: NSA221
vendor: ZyXEL
versions:
status: affected, version: all
}
{
product: NSA310
vendor: ZyXEL
versions:
lessThanOrEqual:  V4.75(AALH.2)C0, status: affected, version:  V4.75(AALH.2)C0, versionType: custom
}
{
product: NSA320
vendor: ZyXEL
versions:
status: affected, version: all
}
{
product: NSA320S
vendor: ZyXEL
versions:
lessThanOrEqual: V4.75(AANV.2)C0, status: affected, version: V4.75(AANV.2)C0, versionType: custom
}
{
product: NSA325
vendor: ZyXEL
versions:
lessThanOrEqual: V4.81(AAAJ.1)C0, status: affected, version: V4.81(AAAJ.1)C0, versionType: custom
}
{
product: NSA325v2
vendor: ZyXEL
versions:
lessThanOrEqual: V4.81(AALS.1)C0, status: affected, version: V4.81(AALS.1)C0, versionType: custom
}
exploits: https://kb.cert.org/artifacts/cve-2020-9054.html
solutions: ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50, VPN100, VPN300, VPN1000, ZyWALL110, ZyWALL310, and ZyWALL1100 devices.
workarounds: Block access to the ZyXEL device web interface:
This issue can be mitigated by blocking (for example with a firewall) access to the web interface (80/tcp and 443/tcp) of any vulnerable ZyXEL device. Any machine that can access the ZyXEL web interface should not also be able to access the internet.
Restrict access to vulnerable ZyXEL devices:
Direct exploitation of this vulnerability can be mitigated by restricting access to vulnerable devices. In particular, do not expose such devices directly to the internet. Note however, that it is still possible for attackers to exploit devices that are not directly connected to the internet. For example, by way of viewing a web page.