ZyXEL NAS products running firmware version 5.21 and earlier are vulnerable to pre-authentication command injection in weblogin.cgi
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: active
- Automatable: no
- Technical impact: total
Summary
ZyXEL network-attached storage (NAS) devices, including models NAS326, NAS520, NAS540, NAS542, and several end-of-support NSA series units, are affected. An unauthenticated remote attacker could exploit a flaw in the login component to run arbitrary commands, potentially gaining full root control of the device.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- CISA SSVC assessment
Exploitation: active · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- ZyXEL NAS326
From V5.21(AAZF.7)C0 · through V5.21(AAZF.7)C0
- ZyXEL NAS520
From V5.21(AASZ.3)C0 · through V5.21(AASZ.3)C0
- ZyXEL NAS540
From V5.21(AATB.4)C0 · through V5.21(AATB.4)C0
- ZyXEL NAS542
From V5.21(ABAG.4)C0 · through V5.21(ABAG.4)C0
- ZyXEL NSA210
all
- ZyXEL NSA220
all
- ZyXEL NSA220+
all
- ZyXEL NSA221
all
- ZyXEL NSA310
From V4.75(AALH.2)C0 · through V4.75(AALH.2)C0
- ZyXEL NSA320
all
- ZyXEL NSA320S
From V4.75(AANV.2)C0 · through V4.75(AANV.2)C0
- ZyXEL NSA325
From V4.81(AAAJ.1)C0 · through V4.81(AAAJ.1)C0
- ZyXEL NSA325v2
From V4.81(AALS.1)C0 · through V4.81(AALS.1)C0