dbcve.org
ExpeditionApplication · Paloaltonetworks

CVE-2024-9464

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 1.2.96 or later.
See remediation →
71/100
Remediation priority · Elevated
High EPSS Remotely reachable 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 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.

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

CVE-2024-9464 is an OS command injection vulnerability in Palo Alto Networks Expedition. An authenticated attacker can inject and execute arbitrary OS commands with root privileges. This enables exfiltration of sensitive data including usernames, cleartext passwords, PAN-OS device configurations, and device API keys stored within or accessible through Expedition.

MitigationApply the vendor patch released by Palo Alto Networks for Expedition. If immediate patching is not possible, restrict network access to Expedition to trusted admin users only and monitor for unauthorized command execution.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed
    Look for Palo Alto Expedition in your environment - typically accessed via web browser on port 443, or check for the application in /opt or similar installation directories. Ask your security team or check asset inventory for 'Expedition' or 'Palo Alto Expedition'.
    Affected if Expedition software is present in the environment
  2. Determine installed Expedition version
    Log into the Expedition web interface and navigate to the Settings or About page to view the version number. Alternatively, check via command line if you have server access: look for version files in the installation directory or run 'expedition --version' if available.
    Affected if Installed version is 1.2.0 through 1.2.95 (inclusive)
  3. Verify version is within vulnerable range
    Compare the found version against the affected range: >= 1.2.0 and < 1.2.96. Any version from 1.2.0 up to and including 1.2.95 is vulnerable.
    Affected if Version falls between 1.2.0 and 1.2.95 inclusive
  4. Confirm authentication is possible
    Determine if the Expedition web interface is accessible and user accounts exist. The vulnerability requires an authenticated session - check if login pages are accessible and active user accounts are configured.
    Affected if Expedition is reachable and accepts authentication credentials

Your environment is affected if Palo Alto Networks Expedition is installed with a version between 1.2.0 and 1.2.95 inclusive and the web interface is accessible to authenticate attackers.

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 the vendor patch released by Palo Alto Networks for Expedition. If immediate patching is not possible, restrict network access to Expedition to trusted admin users only and monitor for unauthorized command execution.

Recommended fix High confidence

Expedition 1.2.96 or later

  1. Back up the current Expedition configuration and any relevant data
  2. Download Expedition version 1.2.96 or later from the Palo Alto Networks support portal
  3. Upgrade Expedition to version 1.2.96 or later following the standard upgrade procedure
  4. Verify the upgrade was successful by checking the Expedition version
  5. Confirm the application is functioning normally and the web interface is accessible

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

Fix this in Expedition Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9464 — 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-9464 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