CVE-2018-9337
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 web interface administration page in PAN-OS 6.1.20 and earlier, PAN-OS 7.1.17 and earlier, PAN-OS 8.0.10 and earlier, and PAN-OS 8.1.1 and earlier may allow an attacker to inject arbitrary JavaScript or HTML.
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 · moderate confidenceThis is a cross-site scripting (XSS) vulnerability in the PAN-OS web-based administration interface. The flaw allows injection of arbitrary JavaScript or HTML through insufficient input validation on the admin login or related pages, likely in a reflected manner.
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.0.0, <= 6.1.20>= 7.1.0, <= 7.1.17> 8.0.0, <= 8.0.10>= 8.1.0, <= 8.1.1CVSS 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.
-
Confirm PAN-OS is installedAccess the device console or SSH and run the command 'show system info' or 'show version' to identify the operating system and versionAffected if The device is not running PAN-OS, then this CVE does not apply
-
Identify the PAN-OS version numberFrom the output of 'show system info' or 'show version', note the exact version number displayed (for example, 7.1.15 or 8.0.9)Affected if No version number is returned or the command fails, the PAN-OS version cannot be determined
-
Compare installed version against affected rangesCheck if the installed version falls into any of these ranges: 6.0.x (any version above 6.0.0 through 6.1.20), 7.1.x (7.1.0 through 7.1.17), 8.0.x (8.0.1 through 8.0.10), or 8.1.x (8.1.0 through 8.1.1). Versions outside these ranges (such as 6.1.21+, 7.1.18+, 8.0.11+, 8.1.2+) are not affectedAffected if The installed version is within any of these ranges: >6.0.0 to <=6.1.20, >=7.1.0 to <=7.1.17, >8.0.0 to <=8.0.10, or >=8.1.0 to <=8.1.1
-
Verify web management interface is enabledRun 'show web-server' or check the management interface settings via the CLI to determine if the PAN-OS web-based administration interface (HTTP or HTTPS) is enabledAffected if The web-based management interface is enabled and accessible, making the XSS vulnerability exploitable
You are affected if the device runs PAN-OS with a version number within any of the four affected ranges AND the web-based administration interface is enabled.
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 6.1.21 or later, 7.1.18 or later, 8.0.11 or later, or 8.1.2 or later. Alternatively, restrict access to the management interface to trusted networks only and disable HTTP/HTTPS management if not required.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9337 — 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-9337 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