KibanaApplication · Elastic
CVE-2020-7013
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 · uneditedKibana versions before 6.8.9 and 7.7.0 contain a prototype pollution flaw in TSVB. An authenticated attacker with privileges to create TSVB visualizations could insert data that would cause Kibana to execute arbitrary code. This could possibly lead to an attacker executing code with the permissions of the Kibana process on the host system.
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 confidencePrototype pollution vulnerability in Kibana's TSVB (Time Series Visual Builder) visualization component allows an authenticated attacker with privileges to create TSVB visualizations to inject malicious data that pollutes JavaScript object prototypes, leading to arbitrary code execution with the permissions of the Kibana process on the host system.
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.9>= 7.0.0, < 7.7.0
Openshift Container PlatformApplication
= 3.11= 4.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 installation and versionRun `kibana --version` or check the Kibana service status and logs for version information. On Linux systems, also check `/usr/share/kibana/package.json` or the installation directory for the version file.Affected if The installed version is less than 6.8.9, or greater than or equal to 7.0.0 but less than 7.7.0
-
Confirm Kibana product (not Elasticsearch)Verify that Kibana is the installed product by checking the service name or process. This vulnerability affects Kibana specifically, not Elasticsearch alone.Affected if Kibana is confirmed as the product and the version is in the affected range from step 1
-
Determine if TSVB visualization feature is accessibleCheck if the TSVB (Time Series Visual Builder) plugin is loaded and accessible. This can be verified by accessing the Kibana UI and attempting to create a new visualization, or by checking the Kibana configuration for enabled plugins.Affected if TSVB is available and users can create visualizations through it
-
Review user privileges for TSVB creationCheck Kibana roles and permissions configuration to identify which users or roles have privileges to create or edit TSVB visualizations. This is typically found in the Kibana security settings or the underlying Elasticsearch roles.Affected if There are users with privileges to create TSVB visualizations, especially if those users are untrusted or low-privilege accounts
You are affected if Kibana is running with a version in the range < 6.8.9 or >= 7.0.0 and < 7.7.0, TSVB visualization feature is accessible, and untrusted or low-privilege users have the ability to create TSVB visualizations.
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.97.7.0
Upgrade Kibana to version 6.8.9 or 7.7.0 or later to remediate this vulnerability. Additionally, limit TSVB visualization creation privileges to trusted, least-privilege users until the upgrade is applied.
Fix this in Kibana
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7013 — 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-7013 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