CVE-2019-1579
Palo Alto Networks PAN-OS Remote Code Execution Vulnerability
Palo Alto Networks PAN-OS
Remote Code Execution in PAN-OS 7.1.18 and earlier, PAN-OS 8.0.11-h1 and earlier, and PAN-OS 8.1.2 and earlier with GlobalProtect Portal or GlobalProtect Gateway Interface enabled may allow an unauthenticated remote attacker to execute arbitrary code.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 10 January 2022. US federal agencies were required to remediate it by 10 July 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 44.2%, which is higher than 98.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2019-1579 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2019-1579.
What does CVE-2019-1579 affect?
CVE-2019-1579 affects Palo Alto Networks PAN-OS. Remote Code Execution in PAN-OS 7.1.18 and earlier, PAN-OS 8.0.11-h1 and earlier, and PAN-OS 8.1.2 and earlier with GlobalProtect Portal or GlobalProtect Gateway Interface enabled may allow an unauthenticated remote attacker to execute arbitrary code.
How severe is CVE-2019-1579?
CVE-2019-1579 is rated HIGH with a CVSS base score of 8.1. EPSS puts the probability of exploitation in the next 30 days at 44.2%, higher than 98.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 July 2022.
How should organisations respond to CVE-2019-1579?
Apply the vendor patch for Palo Alto Networks PAN-OS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.