# CVE-2016-1000219: Information disclosure in n/a

> Attackers can hijack user sessions by reading sensitive cookies and authorization headers from log files when custom logging outputs are configured.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q36m-wm9g-699v

## What is CVE-2016-1000219?

CVE-2016-1000219 is a high-severity vulnerability in Elastic Kibana, published on 16 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2016-1000219?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2016-1000219?

Upgrade to a fixed version.

## Is CVE-2016-1000219 being exploited?

There is no known exploitation of CVE-2016-1000219 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1000219 and fix it if it is affected.

What it is: CVE-2016-1000219 is a high-severity vulnerability in Elastic Kibana, published on 16 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1000219 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1000219/ (Markdown: https://insights.sbomify.com/CVE-2016-1000219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1000219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1000219
- OSV: https://osv.dev/vulnerability/CVE-2016-1000219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1000219/
Summaries are generated and may contain mistakes; the official description above is the record.