dbcve.org
KibanaApplication · Elastic

CVE-2019-7610

CRITICAL · 9.0 CVSS v3.0 Published 2019-03-25
Fix available
A fix is available. Upgrade to 5.6.15 / 6.6.1 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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.6.1 contain an arbitrary code execution flaw in the security audit logger. If a Kibana instance has the setting xpack.security.audit.enabled set to true, an attacker could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with 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 confidence

Kibana versions before 6.6.1 contain an arbitrary code execution vulnerability in the security audit logger. When xpack.security.audit.enabled is set to true, an attacker can send specially crafted requests that attempt to execute JavaScript code, potentially leading to arbitrary command execution with Kibana process permissions on the host system.

MitigationUpgrade Kibana to version 6.6.1 or later. As a temporary workaround, disable the security audit feature by setting xpack.security.audit.enabled to false until the upgrade can be completed.

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:< 5.6.15>= 6.0.0, < 6.6.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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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 checks

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

  1. Determine installed Kibana version
    Run 'kibana --version' or check the Kibana package version installed on your system (e.g., dpkg -l kibana, rpm -qi kibana, or npm list -g kibana)
    Affected if The version is less than 5.6.15, or greater than or equal to 6.0.0 but less than 6.6.1
  2. Locate Kibana configuration file
    Find the kibana.yml configuration file (commonly in /etc/kibana/, /opt/kibana/config/, or the Kibana install root directory)
    Affected if The file exists and contains Kibana settings
  3. Check if security audit is enabled
    Open kibana.yml and search for the setting 'xpack.security.audit.enabled'
    Affected if The setting exists and is set to true (xpack.security.audit.enabled: true)

You are affected only if both your Kibana version is in the vulnerable range (less than 5.6.15, or 6.0.0 to below 6.6.1) AND xpack.security.audit.enabled is set to true in your configuration.

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.

dbcve · scoped
Upgrade available Upgrade to 5.6.15 / 6.6.1 or later
Fixed in 5.6.156.6.1
Interim mitigation

Upgrade Kibana to version 6.6.1 or later. As a temporary workaround, disable the security audit feature by setting xpack.security.audit.enabled to false until the upgrade can be completed.

Recommended fix High confidence

Kibana 5.6.15 (for 5.x users) or Kibana 6.6.1 (for 6.x users)

  1. 1. Determine the currently installed Kibana version by checking the Kibana server or package manager.
  2. 2. If running a 5.x version below 5.6.15, plan upgrade to Kibana 5.6.15.
  3. 3. If running a 6.x version below 6.6.1, plan upgrade to Kibana 6.6.1.
  4. 4. Review the Kibana upgrade documentation for your current version to ensure compatibility.
  5. 5. Before upgrading in production, test the upgrade in a staging environment.
  6. 6. Perform a backup of Kibana configuration and data directories.
  7. 7. Stop the Kibana service.
  8. 8. Upgrade Kibana to the appropriate fixed version (5.6.15 or 6.6.1) using your package manager or by downloading from https://www.elastic.co/downloads/kibana.
Caveat Review Elastic documentation for upgrade considerations between minor versions; ensure plugin compatibility with target version

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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