CriticalCVE-2024-9474

    PAN-OS: Privilege Escalation (PE) Vulnerability in the Web Management Interface (CVE-2024-9474)

    Published In CISA KEV since Sources: SingCERT, pwn.watch, CVE.org

    What is affected, what to do

    A privilege escalation vulnerability in Palo Alto Networks PAN-OS software allows a PAN-OS administrator with access to the management web interface to perform actions on the firewall with root privileges. Cloud NGFW and Prisma Access are not impacted by this vulnerability.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Palo Alto Networks PAN-OS to version 11.2.4-h1, Palo Alto Networks PAN-OS to version 11.1.5-h1, Palo Alto Networks PAN-OS to version 11.0.6-h1. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Palo Alto Networks PAN-OS lt 11.2.0..11.2.4-h1
    • Palo Alto Networks PAN-OS lt 11.1.0..11.1.5-h1
    • Palo Alto Networks PAN-OS lt 11.0.0..11.0.6-h1
    • Palo Alto Networks PAN-OS lt 10.2.0..10.2.12-h2
    • Palo Alto Networks PAN-OS lt 10.1.0..10.1.14-h6
    Fixed in
    • Palo Alto Networks PAN-OS 11.2.4-h1
    • Palo Alto Networks PAN-OS 11.1.5-h1
    • Palo Alto Networks PAN-OS 11.0.6-h1
    • Palo Alto Networks PAN-OS 10.2.12-h2
    • Palo Alto Networks PAN-OS 10.1.14-h6

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.2

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SingCERT, pwn.watch, CVE.org

    93.8 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.84

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    247.64 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), ANSSI / CERT-FR, CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.2 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.9
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    93.8 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.84
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 18 November 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-78

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE sits on the KEV list because it was weaponised in the wild as the second stage of an exploit chain with CVE-2024-0012, pairing an authentication bypass on the PAN-OS web UI with privilege escalation to root — any exposed management interface is effectively takeable without credentials. CISA flags confirmed ransomware-campaign use, and the exploitation likelihood ranks among the highest tracked. Treat it as critical / act within 24 h for any organisation whose PAN-OS MGMT interface has ever been internet-reachable or whose perimeter firewall is unpatched; internal-only MGMT exposure still matters, because a single compromised inside host otherwise inherits the entire perimeter policy. NIS2-regulated operators should assume this is a reportable risk event the moment exposure or an IoC is confirmed.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the fixed PAN-OS release matching your train: 10.1.14-h6, 10.2.12-h2, 11.0.6-h1, 11.1.5-h1 or 11.2.4-h1 (or any later build). Cloud NGFW and Prisma Access are not affected.
      • Remove the management interface of all firewalls and VPN concentrators from the public internet. Restrict TCP/443 and TCP/22 on the MGMT port to a dedicated management network or jump host only, as per Palo Alto's MGMT hardening guidance.
      • Enumerate every account with web-UI access, disable unused ones, rotate credentials for the remaining admins, and regenerate PAN-OS API keys for admin users.
      • Collect forensic evidence before patching: snapshot the running config, export a tech-support file, and preserve /var/log/pan/ plus device telemetry — the patch and subsequent reboot overwrite several artefacts attackers leave behind.
      • If patching cannot start within the day, enforce an ACL on the MGMT interface that only permits a short allow-list of trusted internal IPs; drop all other sources explicitly.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: isolate every PAN-OS appliance into a dedicated out-of-band management VLAN, with no route from user or server segments. Reach it only via a hardened jump host with MFA and session recording.
      • Perimeter hygiene: explicitly block external reachability of web UI, SSH, and API ports on the upstream router/firewall. Validate with an external scan or attack-surface-monitoring tool.
      • IAM hardening: enforce MFA for all PAN-OS administrators (SAML/TACACS+), tighten RBAC to least privilege, and reduce superuser accounts to the absolute minimum. Separate Panorama service accounts from interactive admins.
      • Management-plane monitoring: forward PAN-OS system and config logs to the SIEM via syslog (CEF/LEEF). Alert on every admin login, config commit, and API call outside the change window.
      • Centralised rollout: use Panorama templates and device groups to push patched builds consistently and auditably; patch Panorama itself to the same level.
      • Content updates: install Palo Alto's threat-prevention and application signatures that explicitly cover the CVE-2024-0012 + CVE-2024-9474 exploit chain.

    3. Runbook step 3

      Detection rules

      • Inspect MGMT-interface web access logs for suspicious requests against /php/utils/ and /index.php/.../utils/, especially POSTs with unusual user-agents or from unknown source IPs. KQL sketch: PanOSAccessLogs | where url_path has_any ("php/utils", "/unauth/") and http_method == "POST".
      • Alert on PAN-OS system log entries showing unexpected shell commands, new admin users, or configuration changes outside approved change windows (subtype=config, cmd=set, admin not in known allow-list).
      • Filesystem artefacts: newly created or modified files under /var/appweb/htdocs/, /var/cache/, or cron entries not originating from an official content update. Diff against a known-good tech-support bundle after patching.
      • Network telemetry: Suricata/Zeek rule for POSTs targeting the MGMT IP with base64- or URL-encoded payloads in body or cookies; treat any outbound connection initiated by the firewall MGMT IP as a high-severity alert — the appliance should not speak outbound from that interface.
      • Credential abuse: unusual logins with local admin accounts from new source IPs, repeated MFA failures, or API-key usage outside known automation windows.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A privilege escalation vulnerability in Palo Alto Networks PAN-OS software allows a PAN-OS administrator with access to the management web interface to perform actions on the firewall with root privileges. Cloud NGFW and Prisma Access are not impacted by this vulnerability.

    Source: CSA/SingCERT, pwn.watch, CISA KEV Catalog, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Palo Alto NetworksPAN-OS
    • 11.0.0 – < 11.0.6-h1
    • 10.1.0 – < 10.1.14-h6
    • 11.1.0 – < 11.1.5-h1
    • 11.2.0 – < 11.2.4-h1
    • 10.2.0 – < 10.2.12-h2
    • 11.0.6-h1
    • 10.1.14-h6
    • 11.1.5-h1
    • 11.2.4-h1
    • 10.2.12-h2

    Vendors and products

    Affected operating systems

    Affected operating systems
    Otherpaloaltonetworkspan-os10.1.14
    Otherpaloaltonetworkspan-os10.2.12
    Otherpaloaltonetworkspan-os11.0.6
    Otherpaloaltonetworkspan-os11.1.5
    Otherpaloaltonetworkspan-os11.2.4
    Otherpaloaltonetworkspan-os—

    Weakness classes (CWE)

    • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

      Base

      The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

      Entry at MITRE CWE-78

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of Critical Vulnerability in Palo Alto Networks PAN-OS Software (opens in a new tab)CSA/SingCERTactively exploited
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2024-ALE-015 – [MàJ] Multiples vulnérabilités sur l'interface d'administration des équipements Palo Alto Networks (clôturée 2025-01-27) (opens in a new tab)cert.cyber.gouv.fractively exploited
    GitHubk4nfr3/CVE-2024-9474 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—

    References & sources

    • security.paloaltonetworks.comCVE-2024-9474 PAN-OS: privilege escalation in the management web interfaceVendor advisory, pwn-watch
    • labs.watchtowr.compots-and-pans-aka-an-sslvpn-palo-alto-pan-os-cve-2024-0012-and-…
    • github.comk4nfr3/CVE-2024-9474Exploit
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-9474government-resource
    • unit42.paloaltonetworks.comcve-2024-0012-cve-2024-9474
    • cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2024-ALE-015 – [MàJ] Multiples vulnérabilités sur l'interface d'administration des équipements Palo Alto Networks (clôturée 2025-01-27)cert-fr
    • pwn.watchpwn.watch: Palo Alto PAN-OS management interface auth bypass + privilege escalationpwn-watch
    • security.paloaltonetworks.comCVE-2024-0012 PAN-OS: authentication bypass in the management web interfacepwn-watch
    • NVD (NIST)NVD: CVE-2024-0012pwn-watch
    • NVD (NIST)NVD: CVE-2024-9474pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-9474
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-9474"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-9474.svg?lang=en" alt="CVE-2024-9474 – NEOSEC Intel" height="20"></a>