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

CVE-2020-2021 remediation guide

Palo Alto Networks PAN-OS

When Security Assertion Markup Language (SAML) authentication is enabled and the 'Validate Identity Provider Certificate' option is disabled (unchecked), improper verification of signatures in PAN-OS SAML authentication enables an unauthenticated network-based attacker to access protected resources. The attacker must have network access to the vulnerable server to exploit this vulnerability. This issue affects PAN-OS 9.1 versions earlier than PAN-OS 9.1.3; PAN-OS 9.0 versions earlier than PAN-OS 9.0.9; PAN-OS 8.1 versions earlier than PAN-OS 8.1.15, and all versions of PAN-OS 8.0 (EOL). Thi...

Open CVE record
ProductPalo Alto Networks PAN-OS
Affected versions8.0.*, 8.1, 9.0, 9.1, >= 8.0.0 <= 8.0.20, >= 8.1.0 < 8.1.15, >= 9.0.0 < 9.0.9, >= 9.1.0 < 9.1.3
Fixed versions8.1.15, 9.0.9, 9.1.3
Priority basisImmediate · CVSS 10 · EPSS 4.36%
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.0.*, 8.1, 9.0, 9.1, >= 8.0.0 <= 8.0.20, >= 8.1.0 < 8.1.15, >= 9.0.0 < 9.0.9, >= 9.1.0 < 9.1.3. 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-2020-2021 Remediation Guide | SECUFOCUS NOW