CVE-2018-3817: When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.8% of all records.
- 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.
- Fixed version: grafana (SUSE:HPE Helion OpenStack 8) 4.5.1-4.3.1; kafka (SUSE:HPE Helion OpenStack 8) 0.9.0.1-5.3.1; logstash (SUSE:HPE Helion OpenStack 8) 2.4.1-5.4.1.
Low priority for now. Upgrade to grafana (SUSE:HPE Helion OpenStack 8) 4.5.1-4.3.1; kafka (SUSE:HPE Helion OpenStack 8) 0.9.0.1-5.3.1; logstash (SUSE:HPE Helion OpenStack 8) 2.4.1-5.4.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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% · 63th percentile
- CWE
- CWE-532
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| elastic | logstash | cpe:2.3:a:elastic:logstash |
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
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
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
Published before and after this one in the same product
- ← EarlierCVE-2015-5378Jun 27, 2017 · Logstash 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…31Monitor
- ← EarlierCVE-2015-5619Aug 9, 2017 · Logstash 1.4.x before 1.4.5 and 1.5.x before 1.5.4 with Lumberjack output or the Logstash forwarder does not validate SSL/TLS certificates…23Monitor
- Later →CVE-2021-22138May 13, 2021 · In Logstash versions after 6.4.0 and before 6.8.15 and 7.12.0 a TLS certificate validation flaw was found in the monitoring feature.14Monitor
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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
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
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.