dbcve.org
KibanaApplication · Elastic

CVE-2018-3820

MEDIUM · 6.1 CVSS v3.1 Published 2018-03-30
Fix available
A fix is available. Upgrade to 6.1.3 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
Kibana versions after 6.1.0 and before 6.1.3 had a cross-site scripting (XSS) vulnerability in labs visualizations that could allow an attacker to obtain sensitive information from or perform destructive actions on behalf of other Kibana users.

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

Kibana versions 6.1.1 and 6.1.2 contained a stored cross-site scripting (XSS) vulnerability in the labs visualizations feature. Attackers could inject malicious scripts into labs visualizations that would execute in the browsers of other Kibana users who viewed those visualizations, potentially exposing sensitive data or performing actions on behalf of those users.

MitigationUpgrade Kibana to version 6.1.3 or later to resolve the XSS vulnerability in labs visualizations.

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.1.0, < 6.1.3

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.1/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. Identify installed Kibana version
    Run 'kibana --version' or check the kibana package.json file, or query the Kibana API endpoint /api/status
    Affected if The installed version is 6.1.1 or 6.1.2 (versions greater than 6.1.0 and less than 6.1.3)
  2. Confirm the labs visualizations feature is in use
    Access Kibana and navigate to the Visualize page, then look for any visualizations listed under the 'Labs' category or check if labs visualizations have been created
    Affected if Labs visualizations exist in the Kibana instance and users can view them
  3. Review stored visualizations for script content
    Inspect saved visualization objects in the Kibana .kibana index (via Dev Tools or Elasticsearch query) for any script tags, javascript: URIs, or event handlers in visualization definitions
    Affected if Any visualization contains unsanitized script content that could be executed when viewed by other users

A user is affected if their Kibana version is 6.1.1 or 6.1.2 and the labs visualizations feature is enabled with saved visualizations that could contain injected malicious scripts.

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.1.3 or later
Fixed in 6.1.3
Interim mitigation

Upgrade Kibana to version 6.1.3 or later to resolve the XSS vulnerability in labs visualizations.

Fix this in Kibana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-3820 — 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-2018-3820 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