CVE intelligence and bounded remediation

CVE-2020-1978 — Paloaltonetworks Vm-Series security vulnerability

Medium CVSS 5.8

TechSupport files generated on Palo Alto Networks VM Series firewalls for Microsoft Azure platform configured with high availability (HA) inadvertently collect Azure dashboard service account credentials. These credentials are equivalent to the credentials associated with the Contributor role in Azure. A user with the credentials will be able to manage all the Azure resources in the subscription except for granting access to other resources. These credentials do not allow login access to the VMs themselves. This issue affects VM Series Plugin versions before 1.0.9 for PAN-OS 9.0. This issue does not affect VM Series in non-HA configurations or on other cloud platforms. It does not affect hardware firewall appliances. Since becoming aware of the issue, Palo Alto Networks has safely deleted all the tech support files with the credentials. We now filter and remove these credentials from all TechSupport files sent to us. The TechSupport files uploaded to Palo Alto Networks systems were only accessible by authorized personnel with valid Palo Alto Networks credentials. We do not have any evidence of malicious access or use of these credentials.

Severity
Medium
CVSS
5.8 (3.1)
Published
2020-04-08
CISA KEV
Not currently listed
Ecosystem
windows/system
Weaknesses
CWE-255, CWE-522

Affected products

  • paloaltonetworks / vm-series
  • paloaltonetworks / pan-os / 9.0.0

Matched remediation archetype

Information disclosure and sensitive data exposure

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
  • Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
  • Review metadata, timing, status, length, and existence signals as well as direct content disclosure.

Remediate safely

  • Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
  • Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
  • Update the affected component and add synthetic-data tests for response, error, observability, and export paths.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.