Skip to content
Fencer Intel
medium 6.5

CVE-2018-3817 json

When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive informati…

published 8y ago modified 4mo ago also EUVD-2018-15605

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive information.

Patch / fix

  • elastic logstash 5.6.6, 6.1.2
  • logstash OpenStack Cloud 7 2.4.1-5.1
  • monasca-installer OpenStack Cloud 7 20180608_12.47-9.1
  • kafka OpenStack Cloud 7 0.10.2.2-5.1
  • grafana OpenStack Cloud 7 4.5.1-1.8.1
  • openstack-monasca-installer OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 20180622_15.06-3.6.1
  • kafka OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 0.9.0.1-5.3.1
  • grafana OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 4.5.1-4.3.1
  • logstash OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 2.4.1-5.4.1

suse advisories SUSE-SU-2018:2536-1SUSE-SU-2018:2317-1

Is CVE-2018-3817 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • Elastic Logstash

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.