CVE-2018-10139
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 PAN-OS response for GlobalProtect Gateway in Palo Alto Networks PAN-OS 6.1.21 and earlier, PAN-OS 7.1.18 and earlier, PAN-OS 8.0.11 and earlier may allow an unauthenticated attacker to inject arbitrary JavaScript or HTML. PAN-OS 8.1 is NOT affected.
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 confidenceAn unauthenticated attacker can inject arbitrary JavaScript or HTML into the GlobalProtect Gateway response in Palo Alto Networks PAN-OS versions 6.1.21 and earlier, 7.1.18 and earlier, and 8.0.11 and earlier, resulting in a stored Cross-Site Scripting (XSS) vulnerability. PAN-OS 8.1 is not affected.
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<= 6.1.21>= 7.1.0, <= 7.1.18>= 8.0.0, <= 8.0.11CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 PAN-OS versionAccess the PAN-OS management interface or CLI and retrieve the system version using 'show system info' or check the Dashboard > Device Summary in the web interfaceAffected if The installed version falls within 6.1.21 or earlier, 7.1.0-7.1.18, or 8.0.0-8.0.11 (versions 8.1 and later are not affected)
-
Verify GlobalProtect Gateway is enabledCheck the PAN-OS web interface under Network > GlobalProtect > Gateways, or use CLI 'show global-protect gateway' to list configured gatewaysAffected if Any GlobalProtect Gateway is defined and active in the environment
-
Inspect GlobalProtect Gateway SSL/TLS settingsReview the GlobalProtect Gateway configuration under Network > GlobalProtect > Gateways > SSL/TLS Service Profile, looking for how the portal and gateway respond to authentication requestsAffected if The gateway accepts unauthenticated connections and returns user-controlled content in responses
-
Monitor for anomalous GlobalProtect responsesCapture and review HTTP responses from the GlobalProtect Gateway endpoint for unexpected script tags, HTML markup, or JavaScript code in what should be system-generated contentAffected if Arbitrary JavaScript or HTML appears in stored GlobalProtect Gateway responses that was not authored by the administrator
You are affected if your PAN-OS version is 6.1.21 or earlier, 7.1.0-7.1.18, or 8.0.0-8.0.11 AND you have a GlobalProtect Gateway enabled that can be reached by unauthenticated attackers.
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 PAN-OS to version 7.1.19 or later, 8.0.12 or later, or 8.1 or later to resolve this XSS vulnerability in the GlobalProtect Gateway component.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10139 — 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-10139 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