CVE-2024-0012

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-11-18), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2024-15815 (ENISA EUVD) · GHSA-mw9x-2qwv-599p (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 99.8%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Palo Alto Networks, Inc.) states them: "This issue is fixed in PAN-OS 10.2.12-h2, PAN-OS 11.0.6-h1, PAN-OS 11.1.5-h1, PAN-OS 11.2.4-h1, and all later PAN-OS versions."

An authentication bypass in Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to gain PAN-OS administrator privileges to perform administrative actions, tamper with the configuration, or exploit other authenticated privilege escalation vulnerabilities like CVE-2024-9474 https://security.paloaltonetworks.com/CVE-2024-9474 .

The risk of this issue is greatly reduced if you secure access to the management web interface by restricting access to only trusted internal IP addresses according to our recommended  best practice deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 .

This issue is applicable only to PAN-OS 10.2, PAN-OS 11.0, PAN-OS 11.1, and PAN-OS 11.2 software.

Cloud NGFW and Prisma Access are not impacted by this vulnerability.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
99.8%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Additionally, management interface for affected devices should not be exposed to untrusted networks, including the internet.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://security.paloaltonetworks.com/CVE-2024-0012 · https://nvd.nist.gov/vuln/detail/CVE-2024-0012

Published

November 18, 2024

Last Modified

August 4, 2026

Advisory Details (4)

Auto-updated Oct 27, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-0012
Web page

Pots and Pans, AKA an SSLVPN - Palo Alto PAN-OS CVE-2024-0012 and CVE-2024-9474

https://labs.watchtowr.com/pots-and-pans-aka-an-sslvpn-palo-alto-pan-os-cve-2024-0012-and-cve-2024-9474/
Web page

Threat Brief: Operation Lunar Peek, Activity Related to CVE-2024-0012 and CVE-2024-9474 (Updated Nov. 22)

https://unit42.paloaltonetworks.com/cve-2024-0012-cve-2024-9474/
Web page🟡 PoC Available

CVE-2024-0012 PAN-OS: Authentication Bypass in the Management Web Interface (PAN-SA-2024-0015)

https://security.paloaltonetworks.com/CVE-2024-0012

Vendor Advisories for CVE-2024-0012(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 99× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 925 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 825 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:16 UTCEG score recompute
  2. 2026-11-02 11:16 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-01 08:56 UTCEG score recompute
  4. 2026-11-01 08:56 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  6. 2026-10-31 06:37 UTCEG score recompute
  7. 2026-10-31 06:37 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-30 04:17 UTCEG score recompute
  9. 2026-10-30 04:17 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-29 01:58 UTCEG score recompute
  11. 2026-10-29 01:58 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-27 23:38 UTCEG score recompute
  13. 2026-10-27 23:37 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-27 16:29 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  15. 2026-10-26 21:16 UTCEG score recompute
  16. 2026-10-26 21:16 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-25 18:55 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-25 17:25 UTCEG score recompute
  19. 2026-10-25 16:30 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  20. 2026-10-24 16:35 UTCEG score recompute
  21. 2026-10-24 16:35 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-24 16:29 UTCEPSS rescoreEPSS 99.9% · 99th percentile
  23. 2026-10-23 14:14 UTCEG score recompute
  24. 2026-10-22 11:54 UTCEG score recompute
  25. 2026-10-22 11:54 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-21 09:35 UTCEG score recompute
  2. 2026-10-21 09:34 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-20 07:12 UTCEG score recompute
  4. 2026-10-20 07:12 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-19 04:51 UTCEG score recompute
  6. 2026-10-19 04:51 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-18 07:37 UTCEG score recompute
  8. 2026-10-18 02:30 UTCEG score recompute
  9. 2026-10-18 02:30 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-17 00:09 UTCEG score recompute
  11. 2026-10-17 00:09 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-15 21:48 UTCEG score recompute
  13. 2026-10-15 21:48 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-14 19:28 UTCEG score recompute
  15. 2026-10-14 19:27 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-13 17:06 UTCEG score recompute
  17. 2026-10-13 17:06 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-12 14:44 UTCEG score recompute
  19. 2026-10-12 14:44 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-12 05:54 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-12 01:48 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-11 21:45 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-11 21:35 UTCEG score recompute
  24. 2026-10-11 17:41 UTCEG score recompute
  25. 2026-10-11 17:40 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-11 13:35 UTCEG score recompute
  27. 2026-10-11 13:34 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-11 09:30 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-11 05:25 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-11 01:22 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-10 21:17 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-10 17:12 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-10 13:09 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-10 09:05 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-10 05:02 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-10 00:58 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-09 20:55 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-09 16:51 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-09 12:49 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-09 08:45 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-09 04:39 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-09 00:36 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-08 20:32 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-08 16:29 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-08 12:25 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-08 08:22 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-08 04:18 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-08 00:15 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-07 20:12 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-07 16:09 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-07 12:06 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-07 08:03 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-07 04:00 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-06 23:56 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-06 19:53 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-06 15:50 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-06 11:47 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-06 07:44 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-06 03:41 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-05 23:37 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-05 19:32 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-05 15:29 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-05 11:26 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-05 07:23 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-05 03:19 UTCEG score recompute
  66. 2026-10-05 03:19 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-04 23:20 UTCEPSS rescoreEPSS 99.9% · 99th percentile
  68. 2026-10-04 23:16 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-04 19:12 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-04 15:07 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-04 11:02 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-04 06:59 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-04 02:56 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-03 22:53 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-03 18:50 UTCGHSA enrichmentGHSA-mw9x-2qwv-599p · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(9 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 7 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/panos_management_unauth_rce✓ verified
    Published Dec 30, 2024

    Palo Alto Networks PAN-OS Management Interface Unauthenticated Remote Code Execution

    Open source ↗
  • GitHub PoCRegent8SH/PanOsExploitMultitool
    Published May 21, 2025

    Exploitation and Post-Exploitation Multitool for Palo Alto PAN-OS Systems affected by vulnerabilities CVE-2024-0012 and CVE-2024-9474

    Open source ↗
  • GitHub PoCdcollaoa/cve-2024-0012-gui-poc
    Published Feb 6, 2025

    Python script for CVE-2024-0012 / CVE-2024-9474 exploit

    Open source ↗
  • GitHub PoCTalatumLabs/CVE-2024-0012_CVE-2024-9474_PoC
    Published Dec 11, 2024

    This PoC is targeting vulnerabilities in Palo Alto PAN-OS, specifically CVE-2024-0012 and CVE-2024-9474. This script automates the exploitation process, including payload creation, chunked delivery, and seamless command execution.

    Open source ↗
  • GitHub PoC0xjessie21/CVE-2024-0012
    Published Nov 30, 2024

    CVE-2024-0012 PAN-OS: Authentication Bypass in the Management Web Interface (PAN-SA-2024-0015) RCE POC

    Open source ↗
  • GitHub PoCiSee857/CVE-2024-0012-poc
    Published Nov 22, 2024

    CVE-2024-0012批量检测脚本

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-0012.yaml
    Published Nov 20, 2024

    PAN-OS Management Web Interface - Authentication Bypass

    Open source ↗
  • GitHub PoCSachinart/CVE-2024-0012-POC
    Published Nov 19, 2024

    CVE-2024-0012 PAN-OS: Authentication Bypass in the Management Web Interface (PAN-SA-2024-0015) RCE POC

    Open source ↗
  • GitHub PoCwatchtowrlabs/palo-alto-panos-cve-2024-0012
    Published Nov 19, 2024
    Open source ↗

Frequently asked(6)

What is CVE-2024-0012?
CVE-2024-0012 is a critical-severity vulnerability; its CVE record was published on November 18, 2024. An authentication bypass in Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to gain PAN-OS administrator privileges to perform administrative actions, tamper with the configuration, or exploit other authenticated privilege…
When was CVE-2024-0012 made public?
CVE-2024-0012 was made public on November 18, 2024: that is the date its CVE record's CNA, Palo Alto Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2024. EchelonGraph's copy of the record carries a last-modified date of August 4, 2026; the record at its source may have been updated since.
Is CVE-2024-0012 actively exploited?
Yes. CISA added CVE-2024-0012 to the Known Exploited Vulnerabilities catalog on November 18, 2024, affecting Palo Alto Networks PAN-OS. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2024-0012?
CVE-2024-0012 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2024-0012?
CVE-2024-0012 affects Palo Alto Networks PAN-OS.
How do I remediate CVE-2024-0012?
A fix for CVE-2024-0012 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Palo Alto Networks, Inc.) states them: "This issue is fixed in PAN-OS 10.2.12-h2, PAN-OS 11.0.6-h1, PAN-OS 11.1.5-h1, PAN-OS 11.2.4-h1, and all later PAN-OS versions." The vendor advisories EchelonGraph has for CVE-2024-0012 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-0012

Explore →

Is Your Infrastructure Affected by CVE-2024-0012?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.