KibanaApplication · Elastic
CVE-2016-1000219
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 before 4.5.4 and 4.1.11 when a custom output is configured for logging in, cookies and authorization headers could be written to the log files. This information could be used to hijack sessions of other users when using Kibana behind some form of authentication such as Shield.
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 4.5.4 and 4.1.11 contain a vulnerability where cookies and authorization headers are written to log files when custom logging output is configured. This exposes sensitive authentication credentials that could be harvested by attackers with log file access to hijack user sessions.
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
>= 4.1.0, < 4.1.11>= 4.5.0, < 4.5.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify installed Kibana versionRun 'kibana --version' or check the version field in the kibana.yml configuration file, or inspect the package.json file in the Kibana installation directoryAffected if Version is 4.1.0 through 4.1.10, or 4.5.0 through 4.5.3 (the vulnerable ranges)
-
Locate Kibana configuration fileFind kibana.yml (commonly in /etc/kibana/ or the config/ subdirectory of the Kibana installation)Affected if File exists and can be read - this confirms a Kibana deployment that may be affected
-
Check for custom logging output configurationIn kibana.yml, search for logging.dest, logging.out or similar logging output settings that redirect logs to a custom location (not the default)Affected if Custom logging output is configured to a non-default location (vulnerability only applies when custom logging output is configured)
-
Inspect log files for sensitive dataExamine Kibana log files (at the configured logging destination) for patterns matching 'cookie', 'authorization', or session tokens in plaintextAffected if Log files contain visible cookie values or authorization header contents - this confirms the vulnerability has been triggered
You are affected if Kibana version falls within 4.1.0-4.1.10 or 4.5.0-4.5.3 AND custom logging output is configured, with cookies or authorization headers visible in the log files.
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 data4.1.114.5.4
Upgrade Kibana to version 4.5.4 or later (4.1.11+ for the 4.1.x branch) to remediate this vulnerability. Additionally, restrict access to log files to prevent unauthorized disclosure of credentials.
Fix this in Kibana
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1000219 — 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-2016-1000219 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