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-9463

HIGH · 7.5 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 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 OS command injection vulnerability in Palo Alto Networks Expedition allows an unauthenticated 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

An OS command injection vulnerability in Palo Alto Networks Expedition allows unauthenticated attackers to execute arbitrary OS commands with root privileges, enabling complete compromise of the Expedition system and theft of sensitive credentials including usernames, cleartext passwords, PAN-OS device configurations, and API keys.

MitigationApply the vendor patch immediately, restrict network access to Expedition systems to trusted networks only, and rotate all exposed credentials (usernames, passwords, API keys) and device configurations that may have been disclosed.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Palo Alto Expedition is present
    Check for Expedition running as a service, or locate its installation directory. Common locations include /opt/panos/expedition or checking running processes for 'expedition' or 'Apache' serving Expedition.
    Affected if Expedition software is installed and running in the environment
  2. Determine installed Expedition version
    Access the Expedition web interface and navigate to the About or Settings page to view the version number, or check version files in the installation directory if accessible via CLI.
    Affected if The displayed version is 1.2.0 through 1.2.95 (any version >= 1.2.0 but less than 1.2.96)
  3. Assess network exposure of Expedition interface
    Review firewall rules, reverse proxy configurations, or network access control lists to determine if the Expedition web UI is reachable from untrusted networks.
    Affected if The Expedition web interface is accessible from networks outside trusted management IP ranges

You are affected if Expedition is installed with a version between 1.2.0 and 1.2.95 and its interface is network-accessible.

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 immediately, restrict network access to Expedition systems to trusted networks only, and rotate all exposed credentials (usernames, passwords, API keys) and device configurations that may have been disclosed.

Recommended fix High confidence

1.2.96

  1. Identify the current Expedition version by checking the system or UI
  2. Back up all Expedition data, configurations, and any stored credentials before upgrading
  3. Download Expedition version 1.2.96 or later from the Palo Alto Networks support portal
  4. Upgrade Expedition to the fixed version following the standard upgrade procedure
  5. Verify the upgrade was successful by confirming the new version number in the UI or CLI
  6. Validate that the vulnerability is resolved by reviewing system logs and ensuring no unauthorized access occurred

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

Fix this in Expedition Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,500
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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