nday
CVE-2023-33010

Zyxel Multiple Firewalls Buffer Overflow Vulnerability

Zyxel / Multiple Firewalls, ATP series firmware, USG FLEX series firmware, USG FLEX 50(W) firmware, USG20(W)-VPN firmware, VPN series firmware +1

Added to KEV 12 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

buffer overflow / out-of-bounds write
CWE-120, stated by the CNA Zyxel, NVD's analysts, and NVD, republishing [email protected]
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Zyxel
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Zyxel
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Zyxel
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Zyxel
firewall / VPN / security gateway
affected products in the CVE record: Zyxel · ATP series firmware, Zyxel · USG FLEX 50(W) firmware, Zyxel · USG FLEX series firmware, Zyxel · USG20(W)-VPN firmware, Zyxel · VPN series firmware, Zyxel · ZyWALL/USG series firmwareCPE names NVD's analysts give as vulnerable: o:zyxel:atp100_firmware, o:zyxel:atp100w_firmware, o:zyxel:atp200_firmware, o:zyxel:atp500_firmware, o:zyxel:atp700_firmware, o:zyxel:atp800_firmware, o:zyxel:usg20-vpn_firmware, o:zyxel:usg_20w-vpn_firmware, o:zyxel:usg_40_firmware, o:zyxel:usg_40w_firmware and 13 morenday's type rule zyxel:firewall
stage
KEV
disclosed
disclosure → KEV
T+12d KEV is date-only
cvss
9.8 CRITICAL v3.1
KEV due date
2023-06-26

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2023-05-24T00:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 2023-06-05, inferred from KEV
KEVKEV
2023-06-05, date only

Summary

A buffer overflow vulnerability in the ID processing function in Zyxel ATP series firmware versions 4.32 through 5.36 Patch 1, USG FLEX series firmware versions 4.50 through 5.36 Patch 1, USG FLEX 50(W) firmware versions 4.25 through 5.36 Patch 1, USG20(W)-VPN firmware versions 4.25 through 5.36 Patch 1, VPN series firmware versions 4.30 through 5.36 Patch 1, ZyWALL/USG series firmware versions 4.25 through 4.73 Patch 1, could allow an unauthenticated attacker to cause denial-of-service (DoS) conditions and even a remote code execution on an affected device.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA Zyxel.

Event log

+DISdisclosed

CVE record published by Zyxel. CVSS 9.8, critical. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17293,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-33010",
  "occurred_at": "2023-05-24T00:00:00Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-33010",
      "date_added": "2023-06-05"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 9.8,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2025-01-16T19:00:52.460065Z",
      "automatable": "yes",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2023-05-24T00:00:00.000Z",
    "assigner_short_name": "Zyxel"
  }
}
2023-06-05date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2023-06-26. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 839,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2023-06-05T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-120"
    ],
    "notes": "https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-multiple-buffer-overflow-vulnerabilities-of-firewalls;  https://nvd.nist.gov/vuln/detail/CVE-2023-33010",
    "product": "Multiple Firewalls",
    "due_date": "2023-06-26",
    "precision": "day",
    "date_added": "2023-06-05",
    "vendor_project": "Zyxel",
    "forensic_triage": "No",
    "required_action": "Apply updates per vendor instructions.",
    "vulnerability_name": "Zyxel Multiple Firewalls Buffer Overflow Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2023-06-05inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.