Pan OsOperating system · Paloaltonetworks

CVE-2017-9467

MEDIUM · 6.1 CVSS v3.0 Published 2017-08-02
Fix available
A fix is available. Upgrade to after 6.1.17 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting (XSS) vulnerability in the GlobalProtect external interface in Palo Alto Networks PAN-OS before 6.1.18, 7.x before 7.0.16, 7.1.x before 7.1.11, and 8.x before 8.0.3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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 confidence

A cross-site scripting (XSS) vulnerability exists in the GlobalProtect external interface of Palo Alto Networks PAN-OS. The vulnerability allows remote attackers to inject arbitrary web script or HTML through unspecified vectors, potentially enabling session hijacking or credential theft against users of the GlobalProtect portal.

MitigationUpgrade PAN-OS to version 6.1.18 or later, 7.0.16 or later, 7.1.11 or later, or 8.0.3 or later. Until the upgrade can be performed, consider restricting access to the GlobalProtect external interface using firewall rules or VPN ACLs.

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
Pan OsOperating system
Affected:<= 6.1.17= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.0.7= 7.0.8= 7.0.9= 7.0.10= 7.0.11

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PAN-OS is in use
    Access the device via CLI and run 'show system info' or check the web interface dashboard. Look for 'PAN-OS' or 'Palo Alto Networks' as the operating system.
    Affected if The device is not running PAN-OS, then this CVE does not apply.
  2. Identify the PAN-OS version
    From the 'show system info' output or the web interface dashboard, locate the version number (for example: 7.0.5, 6.1.15, etc.).
    Affected if The version cannot be determined or the device is not PAN-OS.
  3. Check if GlobalProtect external interface is enabled
    In the web interface, go to GlobalProtect > Portals. Verify if a portal is configured and accessible externally. Alternatively, use CLI: 'show global-protect portal <portal-name>' to see configuration details.
    Affected if GlobalProtect portal is not configured or is only accessible internally, the attack surface may be reduced but the vulnerable code may still exist in the software.
  4. Compare installed version against affected ranges
    Check if the version matches: PAN-OS <= 6.1.17 OR PAN-OS = 7.0.1 through 7.0.11 (any of: 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11).
    Affected if The installed version falls within the affected ranges listed, the environment is vulnerable.

If the device runs PAN-OS versions 6.1.17 or lower, or any version from 7.0.1 through 7.0.11, and has GlobalProtect external interface enabled, the environment is affected by this XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 6.1.17
Interim mitigation

Upgrade PAN-OS to version 6.1.18 or later, 7.0.16 or later, 7.1.11 or later, or 8.0.3 or later. Until the upgrade can be performed, consider restricting access to the GlobalProtect external interface using firewall rules or VPN ACLs.

Fix this in Pan Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9467 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9467 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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