KibanaApplication · Elastic
CVE-2019-7608
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 5.6.15 and 6.6.1 had a cross-site scripting (XSS) vulnerability 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 confidenceKibana versions before 5.6.15 and 6.6.1 contained a cross-site scripting (XSS) vulnerability that allowed attackers to inject malicious scripts into Kibana's web interface. This script executes within the context of other authenticated users' sessions, enabling theft of sensitive information or unauthorized actions on behalf of victims.
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
< 5.6.15>= 6.0.0, < 6.6.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Kibana installationIdentify where Kibana is installed. Common locations include /usr/share/kibana, /opt/kibana, or a user-specified directory. If installed via package managers, check the installed package with 'dpkg -l kibana' (Debian) or 'rpm -qi kibana' (RHEL).Affected if Kibana is installed on the system
-
Determine the installed Kibana versionRun 'kibana --version' or 'kibana -V' from the Kibana bin directory. Alternatively, view the version property in the package.json file located in the Kibana installation root directory.Affected if A version number is returned that matches the affected ranges below
-
Compare against affected version rangesCheck if the installed version falls into either of these ranges: less than 5.6.15, or greater than or equal to 6.0.0 but less than 6.6.1. Compare the version strings numerically.Affected if Installed version is < 5.6.15 OR (installed version >= 6.0.0 AND installed version < 6.6.1)
-
Verify Kibana web interface is accessibleConfirm that the Kibana web interface is running and accessible to users. This can be done by accessing the Kibana URL in a browser or checking if the Kibana service is listening on its configured port (default 5601).Affected if Kibana service is running and accessible
A user is affected if Kibana is installed with a version less than 5.6.15 or between 6.0.0 and 6.6.0 (inclusive), and the Kibana web interface is accessible.
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 data5.6.156.6.1
Upgrade Kibana to version 5.6.15 or 6.6.1 or later to remediate this vulnerability.
Fix this in Kibana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7608 — 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-2019-7608 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