ExpeditionApplication · Paloaltonetworks
CVE-2025-0105
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 · uneditedAn arbitrary file deletion vulnerability in Palo Alto Networks Expedition enables an unauthenticated attacker to delete arbitrary files accessible to the www-data user on the host filesystem.
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 confidenceThis is an arbitrary file deletion vulnerability in Palo Alto Networks Expedition that allows unauthenticated attackers to delete any files accessible to the www-data user on the host filesystem, resulting in potential denial of service, data loss, or configuration tampering.
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.101CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Expedition versionAccess the Expedition web UI and navigate to the About or Settings page to view the installed version, or run the command 'expedition-cli --version' via SSH if availableAffected if The displayed version number is lower than 1.2.101 (e.g., 1.2.100, 1.2.50, 1.1.x, etc.)
-
Identify Expedition network exposureReview firewall rules, NAT configurations, or cloud security groups to determine if the Expedition management interface (typically ports 443 or 80) is reachable from external IP addresses or untrusted networksAffected if Expedition is accessible from the internet or from networks outside your trusted internal infrastructure
-
Verify authentication requirementAttempt to access the Expedition login page from an untrusted network or use a tool like curl to send an HTTP request to the Expedition IP: curl -k https://<expedition-ip>/Affected if The login page or any Expedition endpoint responds without requiring credentials, indicating the service is exposed without authentication protection
-
Check for www-data accessible filesReview file permissions on the Expedition host to confirm the www-data user has read/write access to system directories or sensitive configuration filesAffected if The www-data user has broad file system permissions beyond the intended application directory, allowing arbitrary deletion
You are affected if Expedition version is below 1.2.101 AND the management interface is reachable from untrusted networks, as an unauthenticated remote attacker could delete any files the www-data user can access.
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.101
Restrict network access to Expedition to trusted networks only, apply vendor-supplied patches immediately, and monitor for unauthorized file deletion activity.
Expedition 1.2.101 or later
- 1. Back up current Expedition configuration and any important data
- 2. Download Expedition version 1.2.101 or later from the Palo Alto Networks Customer Support Portal
- 3. Install the updated Expedition version following the standard upgrade procedure
- 4. Verify the installation was successful and the web interface is accessible
- 5. Confirm the arbitrary file deletion vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0105 — 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-2025-0105 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