CVE-2024-0012
Exploitation: active CVSS 9.3 CRITICAL Ransomware: known useCVSS base score: 9.3 (Critical) vendor CNA · v4.0
Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one. Vulnrichment source record → (opens in a new tab)
Palo Alto Networks PAN-OS Management Interface Authentication Bypass Vulnerability
Vendor: Palo Alto Networks Product: PAN-OS
Description
Palo Alto Networks PAN-OS contains an authentication bypass vulnerability in the web-based management interface for several PAN-OS products, including firewalls and VPN concentrators.
Research & News Coverage
No mentions found in monitored research blogs or news feeds.
Referenced in Advisories
| Date | Advisory | Issuer |
|---|---|---|
| 2024-12-03 | ICSA-24-338-02: Siemens RUGGEDCOM APE1808 (opens in a new tab) | CISA |
| 2024-11-19 | 2024-117: Zero-Day Vulnerabilities in Palo Alto Networks PAN-OS (opens in a new tab) | CERT-EU |
Lifecycle Timeline
-
2024-11-18
-
2024-11-18Added to CISA KEVListed as known exploited, which starts the federal remediation clock.
-
2024-11-19Public exploit code 1 day laterMetasploit — Palo Alto Networks PAN-OS Management Interface Unauthenticated Remote Code Execution
-
2024-11-19First national advisoryCERT-EU — 2024-117: Zero-Day Vulnerabilities in Palo Alto Networks PAN-OS
-
2024-11-23EPSS flags exploitation risk 4 days laterEntered EPSS already at 96.6%. Dated to the sampled week.
-
2024-12-09Federal remediation due 16 days laterDeadline for federal civilian agencies under BOD 22-01 (since revoked and replaced by BOD 26-04) — now passed.Exposure depends on the asset KEV yes Automatable yes Technical impact total control Window 3 days + forensic triage if exposedCISA KEV
-
not recordedVendor fix publishedNo dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 157 points from 2024-11-23, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 99.9% on 2026-10-02.
Published Applicability
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
Detection & Exploitation
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (opens in a new tab) (CC0) and filtered to repositories that are
still online, contain code, and are starred or at least two weeks old. They are
still not vetted: some are fakes and some are malware. Treat
them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm
an exploit was referenced but carry no date. This product uses data from the
NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0 (opens in a new tab);
its individual Vulnerability Tests are licensed
GNU GPL v2 (opens in a new tab).
| First seen | Tool | Evidence | Earliest reference |
|---|---|---|---|
| 2024-11-19 | Metasploit | Direct — curated exploit code | Palo Alto Networks PAN-OS Management Interface Unauthenticated Remote Code Execution (opens in a new tab) |
| 2024-11-19 | GitHub PoC | Unvetted — public repository | Sachinart/CVE-2024-0012-POC (opens in a new tab) +7 more |
Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.
CISA Assessment (Vulnrichment / SSVC)
Federal Remediation Window (BOD 26-04)
| If the asset is | Remediate within | Table 1 row |
|---|---|---|
| Publicly exposed | 3 days + forensic triage | 1 of 16 |
| Not publicly exposed | 3 days + forensic triage | 9 of 16 |
BOD 26-04 (opens in a new tab) replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.
D3FEND Countermeasures
Defensive techniques inferred by MITRE D3FEND (opens in a new tab) from the underlying weakness (CWE-306) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.