An OS command injection vulnerability in Palo Alto Networks Expedition allows an authenticated attacker to run arbitrary OS commands as root in Expedition, resulting in disclosure of usernames, cleartext passwords, device configurations, and device API keys of PAN-OS firewalls.
CVE-2024-9464
Score elevated to 8.9 because EPSS predicts 82% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.
- High exploitation likelihood — EPSS 82%
- Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 8.9(high)
- EG Risk
- 73(Track*)EG Risk 73/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity89% × 45%Exploitation82% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 82%
- EPSS %ILE
- 100%
- KEV
- Not listed
Published
October 9, 2024
Last Modified
October 17, 2024
References (2)
- psirt@paloaltonetworkshttps://security.paloaltonetworks.com/PAN-SA-2024-0010
- psirt@paloaltonetworkshttps://www.horizon3.ai/attack-research/palo-alto-expedition-from-n-day-to-full-compromise/
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-26 14:53 UTCEPSS rescore
- 2026-07-23 14:17 UTCEPSS rescore
- 2026-07-23 02:47 UTCEG score recompute▼ 0.10
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:07 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
Show 33 moreShow fewer
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-15 17:48 UTCEPSS rescore
- 2026-06-15 17:48 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-12 23:11 UTCEPSS rescore
- 2026-06-12 23:11 UTCEPSS rescore
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:21 UTCEPSS rescore
- 2026-06-10 13:21 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-07 15:24 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-04 13:11 UTCEPSS rescore
- 2026-06-04 13:11 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-26 13:43 UTCEPSS rescore
- 2026-05-26 13:43 UTCEPSS rescore
- 2026-05-26 13:43 UTCEPSS rescore
- 2026-05-23 20:48 UTCEG score recompute
- 2026-05-23 20:48 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoChorizon3ai/CVE-2024-9464First seen Oct 9, 2024
Proof of Concept Exploit for CVE-2024-9464
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2024-9464?
When was CVE-2024-9464 disclosed?
Is CVE-2024-9464 actively exploited?
What is the CVSS score of CVE-2024-9464?
How do I remediate CVE-2024-9464?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-9464
Is Your Infrastructure Affected by CVE-2024-9464?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.