CVE-2016-1000219: High severity elastic vulnerability

Published Jun 16, 2017
·
Updated

Kibana 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.

Affected Software

2 affected components
Elastic Kibana>=4.1.0<4.1.11
Elastic Kibana>=4.5.0<4.5.4

Event History

Jun 16, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-1000219?

CVE-2016-1000219 is considered a moderate severity vulnerability due to the potential for session hijacking.

2

How do I fix CVE-2016-1000219?

To fix CVE-2016-1000219, upgrade to Kibana version 4.5.4 or 4.1.11 or later.

3

What software versions are affected by CVE-2016-1000219?

Kibana versions prior to 4.5.4 and 4.1.11 are affected by CVE-2016-1000219.

4

What type of information could be exposed due to CVE-2016-1000219?

Due to CVE-2016-1000219, cookies and authorization headers could be written to log files, potentially exposing them to unauthorized users.

5

Is CVE-2016-1000219 exploitable remotely?

CVE-2016-1000219 is potentially exploitable remotely if Kibana is configured behind a vulnerable authentication mechanism.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203