KibanaApplication · Elasticsearch
CVE-2020-7017
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 · uneditedIn Kibana versions before 6.8.11 and 7.8.1 the region map visualization in contains a stored XSS flaw. An attacker who is able to edit or create a region map visualization could obtain sensitive information or perform destructive actions on behalf of Kibana users who view the region map visualization.
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 confidenceKibana versions before 6.8.11 and 7.8.1 contain a stored XSS vulnerability in the region map visualization component. An authenticated attacker with privileges to create or edit region map visualizations can inject malicious scripts that execute in the browsers of users who view the compromised visualization, enabling sensitive data theft or destructive actions.
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
KibanaApplication
< 6.8.11>= 7.0.0, < 7.8.1= 12.0.0.3.0= 1.7.0= 8.58CVSS 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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L
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 Kibana versionRun `kibana --version` or check the version file in the Kibana installation directory, or query the Kibana API endpoint `GET /api/status`Affected if version is below 6.8.11, or between 7.0.0 and 7.8.0 (inclusive)
-
Confirm region map plugin is enabledCheck Kibana configuration file (kibana.yml) for `regionmap` entries, or query the saved objects API `GET /api/saved_objects/_find?type=visualization` to look for visualizations with `regionmap` typeAffected if region map visualization feature is present and accessible in the Kibana instance
-
Locate region map visualizationsQuery the saved objects API `GET /api/saved_objects/_find?type=visualization` and filter for those containing 'regionmap' in their JSON, or check the `.kibana` index in Elasticsearch for documents with type 'visualization' and regionmap layer configurationAffected if any region map visualizations exist in the system
-
Inspect visualization definitions for malicious scriptsRetrieve each region map visualization definition via `GET /api/saved_objects/visualization/<id>` and examine the `visState` JSON field for suspicious script tags, iframe embeds, or encoded JavaScript in layer URLs or metadata fieldsAffected if any region map visualization contains unsanitized script content or external resource references
A user is affected if their Kibana version falls in the vulnerable range and there are region map visualizations that could contain injected malicious scripts accessible to 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 data6.8.117.8.1
Upgrade Kibana to version 6.8.11 or later, or 7.8.1 or later. Additionally, review and audit existing region map visualizations for any malicious content introduced before the upgrade.
Fix this in Kibana
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7017 — 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-2020-7017 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