ExpeditionApplication · Paloaltonetworks
CVE-2024-5910
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 · uneditedMissing authentication for a critical function in Palo Alto Networks Expedition can lead to an Expedition admin account takeover for attackers with network access to Expedition. Note: Expedition is a tool aiding in configuration migration, tuning, and enrichment. Configuration secrets, credentials, and other data imported into Expedition is at risk due to this issue.
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 confidencePalo Alto Networks Expedition contains a missing authentication vulnerability for a critical function, allowing unauthenticated attackers with network access to take over Expedition admin accounts. This exposes all configuration secrets, credentials, and sensitive data imported into the Expedition migration tool.
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
>= 1.2.0, < 1.2.92CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Expedition versionAccess the Expedition web interface and locate the version information, typically found in the About, Settings, or System Information section. Alternatively, check any system documentation or package management records if Expedition was installed via package.Affected if Version is 1.2.0 or higher but lower than 1.2.92 (the vulnerable range)
-
Compare version to affected rangeTake the identified version number and compare it against the vulnerable range: >= 1.2.0 and < 1.2.92Affected if The installed version falls within or overlaps the range 1.2.0 through 1.2.91
-
Assess network exposureDetermine if Expedition web interface is reachable from network locations outside the trusted administrative network. Check firewall rules, NAT configurations, or reverse proxy settings that expose Expedition.Affected if Expedition is network-accessible from untrusted or external networks while running a vulnerable version
Environment is affected if Expedition version is 1.2.0 or higher but lower than 1.2.92 AND the system is accessible over a network where untrusted actors could reach the unauthenticated function
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.2.92
Restrict network access to Expedition systems immediately and apply the vendor patch when available. Audit for any compromised accounts and rotate exposed credentials.
1.2.92 or later
- 1. Identify the current Expedition version by navigating to the Expedition web interface or checking system documentation
- 2. If the current version is >= 1.2.0 and < 1.2.92, plan for an upgrade
- 3. Back up all Expedition configuration data, imported configurations, and any stored credentials before upgrading
- 4. Obtain the upgrade package from the official Palo Alto Networks support portal or authorized distribution channel
- 5. Follow Palo Alto Networks documentation to perform the upgrade to version 1.2.92 or later
- 6. After upgrade, verify the Expedition application is running correctly
- 7. Review admin accounts and reset credentials as a precautionary measure since the vulnerability allowed admin account takeover
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5910 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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