When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive informatio
When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive information.
- Published
- Mar 30, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 62th percentile
- CWE
- CWE-532
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| elastic | logstash | cpe:2.3:a:elastic:logstash |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- elastic logstashbefore 5.6.6
- elastic logstash6.0.0 and later · before 6.1.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (elastic). Independent of NVD's CPE analysis and usually ahead of it.
Elastic Logstash
- Before 6.1.2 or 5.6.6affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| SUSE:HPE Helion OpenStack 8 | grafana | before 4.5.1-4.3.1 | 4.5.1-4.3.1 |
| SUSE:HPE Helion OpenStack 8 | kafka | before 0.9.0.1-5.3.1 | 0.9.0.1-5.3.1 |
| SUSE:HPE Helion OpenStack 8 | logstash | before 2.4.1-5.4.1 | 2.4.1-5.4.1 |
| SUSE:HPE Helion OpenStack 8 | openstack-monasca-installer | before 20180622_15.06-3.6.1 | 20180622_15.06-3.6.1 |
| SUSE:OpenStack Cloud 7 | grafana | before 4.5.1-1.8.1 | 4.5.1-1.8.1 |
| SUSE:OpenStack Cloud 7 | kafka | before 0.10.2.2-5.1 | 0.10.2.2-5.1 |
| SUSE:OpenStack Cloud 7 | logstash | before 2.4.1-5.1 | 2.4.1-5.1 |
| SUSE:OpenStack Cloud 7 | monasca-installer | before 20180608_12.47-9.1 | 20180608_12.47-9.1 |
Same product
elastic: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-7612A sensitive data disclosure flaw was found in the way Logstash versions before 5.6.15 and 6.6.1 logs malformed URLs.40Plan
- CVE-2026-33466Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write39Monitor
- CVE-2019-7620Logstash versions before 7.4.1 and 6.8.4 contain a denial of service flaw in the Logstash Beats input plugin.31Monitor
- CVE-2015-5378Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read communications between Logstash Forwarder agent and Logst31Monitor
- CVE-2016-1000221Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive info31Monitor
- CVE-2014-4326Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) za31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| suse:grafana | 4.5.1-4.3.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:kafka | 0.9.0.1-5.3.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:logstash | 2.4.1-5.4.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:monasca-installer | 20180608_12.47-9.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:openstack-monasca-installer | 20180622_15.06-3.6.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.