dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 Dec 2024.
ExpeditionApplication · Paloaltonetworks

CVE-2024-9465

CRITICAL · 9.1 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 1.2.96 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Palo Alto Networks Expedition enables unauthenticated attackers to dump the database (including password hashes, usernames, device configurations, and API keys) and read/write arbitrary files on the system. This is a critical pre-authentication flaw with complete system compromise potential.

MitigationApply vendor patch immediately; if no patch available, restrict network access to Expedition or disable the service until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ExpeditionApplication
Affected:>= 1.2.0, < 1.2.96

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Expedition is deployed
    Inventory your environment for Palo Alto Networks Expedition installations, checking running services, installed applications, or containers
    Affected if Expedition is present in the environment
  2. Determine Expedition version
    Locate the installed version through the Expedition web interface, command line, or configuration files shipped with the product
    Affected if Version cannot be determined or is not visible
  3. Compare version against affected range
    Check if the installed version falls within >=1.2.0 and <1.2.96
    Affected if Installed version is 1.2.0 through 1.2.95
  4. Assess network exposure
    Determine if the Expedition web interface is accessible from untrusted networks or the internet
    Affected if Expedition is network-accessible without VPN or proper access controls

User is affected if Expedition version is 1.2.0 through 1.2.95 and the web interface is exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.96 or later
Fixed in 1.2.96
Interim mitigation

Apply vendor patch immediately; if no patch available, restrict network access to Expedition or disable the service until patched.

Recommended fix High confidence

Expedition version 1.2.96 or later

  1. Verify current Expedition version by accessing the Expedition web interface or checking system information
  2. Download the fixed Expedition version 1.2.96 (or later) from the Palo Alto Networks Customer Support Portal
  3. Review Palo Alto Networks upgrade documentation for Expedition before proceeding
  4. Perform a backup of the current Expedition configuration and database
  5. Follow the official Palo Alto Networks upgrade procedure to install version 1.2.96 or later
  6. After upgrade, verify the Expedition interface is accessible and functioning normally
  7. Confirm the SQL injection vulnerability is remediated by verifying the fix
Caveat Review Expedition release notes for any configuration or migration requirements when upgrading between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Expedition Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data