CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2023-33010 remediation guide

Zyxel Multiple Firewalls

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.

Open CVE record
ProductZyxel Multiple Firewalls
Affected versions4.32 through 5.36 Patch 1, 4.50 through 5.36 Patch 1, 4.25 through 5.36 Patch 1, 4.30 through 5.36 Patch 1, 4.25 through 4.73 Patch 1, >= 4.32 < 5.36, 5.36, >= 4.50 < 5.36, >= 4.25 < 5.36, >= 4.30 < 5.36, >= 4.25 < 4.73, 4.73
Fixed versions5.36, 4.73
Priority basisImmediate · CVSS 9.8 · EPSS 28.8%
01

Identify the affected asset

Confirm whether Zyxel Multiple Firewalls is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 4.32 through 5.36 Patch 1, 4.50 through 5.36 Patch 1, 4.25 through 5.36 Patch 1, 4.30 through 5.36 Patch 1, 4.25 through 4.73 Patch 1, >= 4.32 < 5.36, 5.36, >= 4.50 < 5.36, >= 4.25 < 5.36, >= 4.30 < 5.36, >= 4.25 < 4.73, 4.73. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.