CVE-2016-1000221 Logstash Logs Sensitive Information
An attacker with access to Logstash logs can read sensitive HTTP authorization headers due to improper logging practices in the Elasticsearch output plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-1000221?
CVE-2016-1000221 is a high-severity vulnerability in n/a, published on 16 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive information.
Weakness: CWE-200
Which versions are affected by CVE-2016-1000221?
2 open source packages ship an affected version, including logstash-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
logstash-core RubyGems | All versions | 2.3.4 |
logstash-core RubyGems | All versions | 2.3.4 |
Products include Elastic Logstash.
How do I fix CVE-2016-1000221?
Upgrade logstash-core to 2.3.4 or later.
Is CVE-2016-1000221 being exploited?
There is no known exploitation of CVE-2016-1000221 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2019-7612 Information disclosure in Logstash
- CVE-2023-46672 Logstash Insertion of Sensitive Information into Log File
- CVE-2026-33466 Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write
- CVE-2019-7620 Denial of service in Logstash
- CVE-2015-5378 Information disclosure in n/a
Sources
Also known as GHSA-vcmm-ppqx-95ch.