Improper error message handling in Zyxel ZyWALL/USG series firmware versions 4.60 through 4.73, VPN series firmware versions 4.60 through 5…
Improper error message handling in Zyxel ZyWALL/USG series firmware versions 4.60 through 4.73, VPN series firmware versions 4.60 through 5.35, USG FLEX series firmware versions 4.60 through 5.35, and ATP series firmware versions 4.60 through 5.35, which could allow an unauthenticated attacker to execute some OS commands remotely by sending crafted packets to an affected device.
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
https://cwe.mitre.org/data/definitions/78.html →Open in CWE collection →An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
https://capec.mitre.org/data/definitions/6.html →Open in CAPEC collection →An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
https://capec.mitre.org/data/definitions/15.html →Open in CAPEC collection →An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
https://capec.mitre.org/data/definitions/43.html →Open in CAPEC collection →In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.
https://capec.mitre.org/data/definitions/88.html →Open in CAPEC collection →An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
https://capec.mitre.org/data/definitions/108.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| atp100_firmware | * | Exploited |
| atp100w_firmware | * | Exploited |
| atp200_firmware | * | Exploited |
| atp500_firmware | * | Exploited |
| atp700_firmware | * | Exploited |
| atp800_firmware | * | Exploited |
| usg_flex_100_firmware | * | Exploited |
| usg_flex_100w_firmware | * | Exploited |
| usg_flex_200_firmware | * | Exploited |
| usg_flex_500_firmware | * | Exploited |
| usg_flex_50_firmware | * | Exploited |
| usg_flex_50w_firmware | * | Exploited |
| usg_flex_700_firmware | * | Exploited |
| vpn1000_firmware | * | Exploited |
| vpn100_firmware | * | Exploited |
| vpn300_firmware | * | Exploited |
| vpn50_firmware | * | Exploited |
| zywall_usg_100_firmware | * | Exploited |
| zywall_usg_310_firmware | * | Exploited |