CVE-2023-33010VulnerabilityPublished 24 May 2023Updated 21 Oct 2025

CVE-2023-33010: Zyxel ATP series firmware · Classic Buffer Overflow

Affects Zyxel ATP series firmwareSource CVE Database V5

Exploited in the wild · KEV due 26 Jun 2023 · 29% EPSS : apply the vendor's fix or mitigations to Zyxel ATP series firmware now.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 26 Jun 2023 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 29.0% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: 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.
Confidentiality: High: There is 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.
Integrity: 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: High: There is 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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 24 May 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 12 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Zyxel
2023-05-17, 7 days before disclosure
CVE published
on cve.org
2023-05-24, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2023-06-05, 12 days after disclosure
KEV remediation due
US federal deadline
2023-06-26, 33 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply updates per vendor instructions.

Affected software

Product	Affected	Fixed in
Zyxel ATP series firmware	Affected >=4.32 <=5.36	Fixed in–

Check the firmware or software version for Zyxel ATP series firmware in the device's admin interface against the vendor advisory.

Description

CVE-2023-33010 is a critical buffer overflow vulnerability in multiple Zyxel firewall and VPN device firmware versions, including ATP, USG FLEX, USG20(W)-VPN, and ZyWALL/USG series. The flaw exists in the ID processing function and allows an unauthenticated attacker to remotely execute code or cause denial-of-service conditions. It affects firmware versions ranging approximately from 4.25 to 5.36 Patch 1, depending on the product line. The vulnerability has a CVSS score of 9.8, indicating high exploitability without authentication or user interaction. Although no known exploits are currently reported in the wild, the potential impact on confidentiality, integrity, and availability is severe. European organizations using Zyxel network security appliances are at risk, especially those in critical infrastructure, government, and enterprises relying on these devices for perimeter defense. Mitigation requires immediate firmware updates once patches are available, network segmentation, and monitoring for anomalous traffic targeting these devices.

Impact

The impact of CVE-2023-33010 on European organizations is substantial due to the widespread use of Zyxel network security appliances in enterprise, government, and critical infrastructure sectors. Exploitation could allow attackers to bypass perimeter defenses, gain unauthorized access to internal networks, exfiltrate sensitive data, disrupt business operations via denial-of-service, or establish persistent footholds for further attacks. Confidentiality is at high risk as attackers could intercept or manipulate network traffic. Integrity and availability are also severely affected, as remote code execution could lead to device compromise or outages. Given the critical role of these devices in securing VPN connections and network boundaries, exploitation could have cascading effects on organizational security posture. European organizations with limited patch management capabilities or those operating in high-threat environments are particularly vulnerable. The absence of known exploits in the wild currently provides a window for proactive defense, but the critical severity demands urgent attention.

Mitigation

1. Immediately inventory all Zyxel devices in use, identifying firmware versions to assess exposure. 2. Monitor Zyxel’s official channels for firmware patches addressing CVE-2023-33010 and prioritize rapid deployment once available. 3. Until patches are applied, implement network segmentation to isolate vulnerable devices from critical assets and limit exposure. 4. Employ strict ingress filtering and firewall rules to restrict access to management interfaces and services exposed to untrusted networks. 5. Deploy intrusion detection/prevention systems (IDS/IPS) with updated signatures to detect anomalous traffic patterns targeting Zyxel devices. 6. Conduct regular network traffic analysis to identify suspicious packets that could exploit the buffer overflow. 7. Enforce multi-factor authentication and strong access controls on device management interfaces to reduce risk of lateral movement post-exploitation. 8. Maintain up-to-date backups and incident response plans tailored to network device compromise scenarios. 9. Engage with Zyxel support for guidance and early access to patches or mitigations if possible. 10. Educate network operations teams about the vulnerability specifics to enhance detection and response capabilities.

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2025, 23:48 UTC

WeaknessesCWE-120

Technical details

References

Community reviews

Related threats