ExpeditionApplication · Paloaltonetworks
CVE-2018-10142
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 · uneditedThe Expedition Migration tool 1.0.106 and earlier may allow an unauthenticated attacker to enumerate files on the operating system.
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 confidenceThe Expedition Migration tool versions 1.0.106 and earlier contains a file enumeration vulnerability that allows unauthenticated attackers to traverse directories and enumerate files on the host operating system via the web interface.
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.0.106CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Expedition Migration tool is installedCheck for the presence of Palo Alto Expedition on the system. Look for Expedition installation directories, services, or running processes related to Expedition.Affected if Expedition Migration tool is found running on the system
-
Determine the installed Expedition versionLocate and read the Expedition version information. Check installation files, configuration files, or the application itself for the version number (typically found in about pages, version files, or the web interface header).Affected if The version is 1.0.106 or earlier (any version up to and including 1.0.106)
-
Verify the web interface is accessibleCheck if the Expedition web interface port (commonly port 443 or as configured) is listening and responding. Confirm network accessibility from external sources.Affected if The Expedition web interface is exposed and reachable over the network
-
Confirm directory traversal is possibleTest the web interface for directory traversal by attempting to access paths outside the expected application directories (such as ../../etc/passwd or similar path traversal patterns in URL parameters).Affected if The application allows traversing beyond its intended directory structure, enumerating files outside the application root
A system is affected if it is running Palo Alto Networks Expedition version 1.0.106 or earlier with its web interface accessible, since the directory traversal vulnerability can be exploited without authentication.
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.
From vendor dataUpgrade to a version later than 1.0.106. If upgrading is not immediately possible, restrict network access to the Expedition Migration tool interface to trusted sources only.
Fix this in Expedition
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10142 — 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-2018-10142 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