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

CVE-2022-0028 remediation guide

Palo Alto Networks PAN-OS

A PAN-OS URL filtering policy misconfiguration could allow a network-based attacker to conduct reflected and amplified TCP denial-of-service (RDoS) attacks. The DoS attack would appear to originate from a Palo Alto Networks PA-Series (hardware), VM-Series (virtual) and CN-Series (container) firewall against an attacker-specified target. To be misused by an external attacker, the firewall configuration must have a URL filtering profile with one or more blocked categories assigned to a source zone that has an external facing interface. This configuration is not typical for URL filtering and,...

Open CVE record
ProductPalo Alto Networks PAN-OS
Affected versions8.1, 9.0, 9.1, 10.0, 10.1, 10.2, 8.1.0, 9.0.0, 9.1.0, 10.0.0, 10.1.0, 10.2.0, >= 8.1.0 < 8.1.23, >= 9.0.0 < 9.0.16, >= 9.1.0 < 9.1.14, >= 10.0.0 < 10.0.11, >= 10.1.0 < 10.1.6, >= 10.2.0 < 10.2.2, 8.1.23, 9.0.16
Fixed versions8.1.23, 9.0.16, 9.1.14, 10.0.11, 10.1.6, 10.2.2
Priority basisImmediate · CVSS 8.6 · EPSS 2.13%
01

Identify the affected asset

Confirm whether Palo Alto Networks PAN-OS 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: 8.1, 9.0, 9.1, 10.0, 10.1, 10.2, 8.1.0, 9.0.0, 9.1.0, 10.0.0, 10.1.0, 10.2.0, >= 8.1.0 < 8.1.23, >= 9.0.0 < 9.0.16, >= 9.1.0 < 9.1.14, >= 10.0.0 < 10.0.11, >= 10.1.0 < 10.1.6, >= 10.2.0 < 10.2.2, 8.1.23, 9.0.16. 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.

CVE-2022-0028 Remediation Guide | SECUFOCUS NOW