dbcve.org
KibanaApplication · Elastic

CVE-2020-7015

MEDIUM · 5.4 CVSS v3.1 Published 2020-06-03
Fix available
A fix is available. Upgrade to 6.8.10 / 7.7.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Kibana versions before 6.8.9 and 7.7.0 contains a stored XSS flaw in the TSVB visualization. An attacker who is able to edit or create a TSVB visualization could allow the attacker to obtain sensitive information from, or perform destructive actions, on behalf of Kibana users who edit the TSVB 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in the TSVB (Time Series Visual Builder) visualization component of Kibana. An attacker with the ability to create or edit TSVB visualizations can inject malicious scripts that execute when other Kibana users subsequently edit those same visualizations, potentially allowing sensitive information theft or destructive actions.

MitigationUpgrade Kibana to version 6.8.9 or 7.7.0 or later. Until patches can be applied, restrict creation and editing privileges of TSVB visualizations to trusted users only.

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
Affected:< 6.8.10>= 7.0.0, < 7.7.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

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

  1. Identify your Kibana version
    Check the Kibana server log at startup or the Kibana About page (Kibana > Management > About). Alternatively, check the installed package: rpm -q kibana or dpkg -l kibana depending on your OS.
    Affected if The installed version is less than 6.8.10, or greater than or equal to 7.0.0 but less than 7.7.1
  2. Confirm TSVB visualization feature is accessible
    Verify if the Kibana instance has the Visualize app enabled and accessible. Navigate to Kibana > Visualize and attempt to create a new visualization to see if TSVB (Time Series Visual Builder) is available as a visualization type.
    Affected if TSVB visualization type is listed and accessible in the Visualize editor
  3. Identify who can create or edit TSVB visualizations
    Review Kibana roles and permissions in Management > Security > Roles. Check for roles with the create_shortcut, save, and write privileges on the visualizations index, or inspect the .kibana index for users with editor access.
    Affected if Untrusted users or users outside your security team have create or edit permissions for visualizations
  4. Inspect existing TSVB visualizations for injected content
    Query the .kibana index (or use Dev Tools) for saved objects of type visualization that contain 'visualization' in the search id and inspect their JSON for any suspicious script tags, event handlers, or encoded payloads in the TSVB configuration.
    Affected if Any TSVB visualization contains script tags, javascript: URLs, or on* event handlers in its configuration

You are affected if running a Kibana version in the vulnerable range and untrusted users have the ability to create or edit TSVB visualizations that could be subsequently opened by other users.

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 6.8.10 / 7.7.1 or later
Fixed in 6.8.107.7.1
Interim mitigation

Upgrade Kibana to version 6.8.9 or 7.7.0 or later. Until patches can be applied, restrict creation and editing privileges of TSVB visualizations to trusted users only.

Fix this in Kibana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2020-7015 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