Threats / Palo Alto Networks / CVE-2024-9465
CVE-2024-9465
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Palo Alto Networks Expedition vulnerability
Palo Alto Networks Expedition contains a SQL injection vulnerability allowing unauthenticated attackers to extract sensitive database contents including password hashes, usernames, device configurations, and API keys, plus read and create a
Verdict
Today item — known-exploited.
Unauthenticated SQL injection in a network management tool enables direct database compromise and file system access without credentials, exposing authentication material and infrastructure configurations at scale.
CISA KEV Yes · 2024-11-145EPSS 0.99609 (verify live)6Exploit Weaponized · public PoC7CVSS 9.23CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
296 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-14).
Probability (EPSS)
EPSS 0.99609 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.2 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N/AU:N/R:U/V:C/RE:H/U:Amber) · Affected: Palo Alto Networks, Expedition. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 36 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious SQL queries in Expedition requests to bypass authentication and access the backend database.
Business
Attackers gain immediate database access without valid credentials, eliminating the authentication control layer.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract password hashes, usernames, API keys, and device configurations from the compromised database.
Business
Credential material and infrastructure secrets are exposed, enabling lateral movement and further system compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage file read and write capabilities to access or modify system files on the Expedition host.
Business
Attackers achieve arbitrary code execution potential and persistent access through file manipulation.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by palo_altoCNA
Credited with finding itZach Hanley (@hacks_zach) of Horizon3.aifinderEnrique Castillo of Palo Alto Networksfinder