# CVE-2024-9465: Palo Alto Networks Expedition SQL Injection

> Unauthenticated attackers can exploit SQL injection to steal credentials and execute arbitrary code on Palo Alto Expedition servers.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Yes, since 14 Nov 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9f2c-45xq-c486

## What is CVE-2024-9465?

CVE-2024-9465 is a critical SQL injection vulnerability in Palo Alto Networks Expedition, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SQL injection vulnerability in Palo Alto Networks Expedition allows an unauthenticated attacker to reveal Expedition database contents, such as password hashes, usernames, device configurations, and device API keys. With this, attackers can also create and read arbitrary files on the Expedition system.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-9465?

It affects 1 product.


Products: Paloaltonetworks Expedition.

## How do I fix CVE-2024-9465?

No fix has been published for CVE-2024-9465 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Dec 2024.

## Is CVE-2024-9465 being exploited?

Yes. Attackers have exploited CVE-2024-9465 in the wild since at least 14 Nov 2024.

Public exploit code:

- Proof of Concept Exploit for CVE-2024-9465 (github_poc): https://github.com/horizon3ai/CVE-2024-9465
- Checkpoint SQL Injection via Time-Based Attack (CVE-2024-9465) (github_poc): https://github.com/mustafaakalin/CVE-2024-9465
- Checkpoint SQL Injection via Time-Based Attack (CVE-2024-9465) (github_poc): https://github.com/Qlng/CVE-2024-9465
- Palo Alto Expedition - SQL Injection (nuclei): http/cves/2024/CVE-2024-9465.yaml

## Other vulnerabilities in Palo Alto Networks Expedition

- [CVE-2024-9463](https://insights.sbomify.com/CVE-2024-9463/): Palo Alto Networks Expedition OS Command Injection (critical 9.9, exploited in the wild)
- [CVE-2024-5910](https://insights.sbomify.com/CVE-2024-5910/): Palo Alto Networks Expedition Missing Authentication (critical 9.3, exploited in the wild)
- [CVE-2018-10143](https://insights.sbomify.com/CVE-2018-10143/): Command injection in Palo Alto Networks Expedition (critical 9.8)
- [CVE-2024-9464](https://insights.sbomify.com/CVE-2024-9464/): Expedition: Authenticated OS Command Injection Vulnerability Leads to Firewall Admin Credential Disclosure (critical 9.3)
- [CVE-2025-0103](https://insights.sbomify.com/CVE-2025-0103/): Expedition: SQL Injection Vulnerability (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9465 and fix it if it is affected.

What it is: CVE-2024-9465 is a critical SQL injection vulnerability in Palo Alto Networks Expedition, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-9465 in the wild since at least 14 Nov 2024.

Affected product: Palo Alto Networks Expedition. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-9465/ (Markdown: https://insights.sbomify.com/CVE-2024-9465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9465
- OSV: https://osv.dev/vulnerability/CVE-2024-9465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-9465/
Summaries are generated and may contain mistakes; the official description above is the record.