Expedition Migration ToolApplication · Paloaltonetworks
CVE-2019-1567
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.1.6 and earlier may allow an authenticated attacker to run arbitrary JavaScript or HTML in the User Mapping Settings.
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 a Cross-Site Scripting (XSS) vulnerability in the Expedition Migration tool versions 1.1.6 and earlier. An authenticated attacker can inject arbitrary JavaScript or HTML code into the User Mapping Settings, which will then execute in the context of other users viewing those settings.
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
Expedition Migration ToolApplication
<= 1.1.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installedLocate the Expedition tool installation directory or check for the application in your system. Common paths may include /opt/expedition or a dedicated application folder. Look for expedition-related processes or web interfaces.Affected if The product is present on the system
-
Determine the installed version of Expedition Migration ToolCheck the version number typically found in the application interface, in an about section, in a version file within the installation directory, or via a command-line version flag if available.Affected if The version is 1.1.6 or earlier
-
Verify User Mapping Settings functionality is accessibleAccess the Expedition Migration Tool web interface or configuration panel and navigate to the User Mapping Settings area. Check if this feature is enabled and accessible to authenticated users.Affected if User Mapping Settings are present and accessible to authenticated users
-
Check for existing XSS payloads in User Mapping SettingsIf you have admin access, review the User Mapping Settings configuration for any unexpected or suspicious script tags, HTML elements, or encoded content that may indicate prior exploitation.Affected if Unexpected script or HTML content is found in User Mapping Settings
A user is affected if Expedition Migration Tool version 1.1.6 or earlier is installed and the User Mapping Settings feature is accessible to authenticated users.
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 newer than 1.1.6 that includes proper input sanitization and output encoding for the User Mapping Settings functionality. If upgrade is not immediately possible, restrict administrative access to the User Mapping Settings area.
Fix this in Expedition Migration Tool
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1567 — 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-2019-1567 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