dbcve.org
ExpeditionApplication · Paloaltonetworks

CVE-2024-9466

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
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
A cleartext storage of sensitive information vulnerability in Palo Alto Networks Expedition allows an authenticated attacker to reveal firewall usernames, passwords, and API keys generated using those credentials.

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

Palo Alto Networks Expedition stores firewall usernames, passwords, and API keys in cleartext (unencrypted) format. An authenticated attacker with access to Expedition can read these stored credentials, potentially gaining unauthorized access to firewall management functions and sensitive network infrastructure.

MitigationUpgrade to the patched version of Palo Alto Networks Expedition when available. Rotate all exposed firewall credentials (usernames, passwords, API keys) that may have been stored in the affected system as a precautionary measure.

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
    Locate the Palo Alto Networks Expedition installation on your system. Check for the Expedition application directory, service, or web interface accessible on the server.
    Affected if Expedition is present on the system
  2. Check Expedition version
    Determine the installed version of Palo Alto Networks Expedition. This can typically be done via the web UI (usually in About or Settings), command line (such as 'expedition --version' or checking package manager), or by inspecting version files in the installation directory.
    Affected if The installed version is 1.2.0 or higher but lower than 1.2.96
  3. Examine credential storage locations
    Inspect Expedition's configuration files, databases, or credential storage areas for stored firewall credentials. Look for files or database entries containing usernames, passwords, and API keys associated with firewall management.
    Affected if Credentials are found stored in cleartext (unencrypted) format rather than being hashed or encrypted

You are affected if Palo Alto Networks Expedition version 1.2.0 through 1.2.95 is installed and contains firewall credentials stored in cleartext format.

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

Upgrade to the patched version of Palo Alto Networks Expedition when available. Rotate all exposed firewall credentials (usernames, passwords, API keys) that may have been stored in the affected system as a precautionary measure.

Recommended fix High confidence

Expedition version 1.2.96 or later

  1. 1. Back up the current Expedition configuration and any migration projects before upgrading.
  2. 2. Download the Expedition version 1.2.96 or later from the Palo Alto Networks support portal.
  3. 3. Stop the Expedition service before performing the upgrade.
  4. 4. Install the Expedition 1.2.96 (or later) update/package using the standard upgrade procedure.
  5. 5. After upgrade, verify the service is running correctly.
  6. 6. Review and clear any existing log files that may contain sensitive information stored in cleartext.
  7. 7. Validate that new logs do not contain sensitive credentials in cleartext.

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

Fix this in Expedition Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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