nday
CVE-2016-10362

Elastic Logstash: information disclosureTitle composed by nday; the CVE record has none.

Elastic / Logstash

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

information disclosure
CWE-200, stated by NVD's analystsCWE-532, stated by the CNA elastic and NVD, republishing [email protected]
network
AV:N in CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (CVSS 3.0) from NVD's analysts
no user interaction
UI:N in CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (CVSS 3.0) from NVD's analysts
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2017-06-16T21:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

Prior to Logstash version 5.0.1, Elasticsearch Output plugin when updating connections after sniffing, would log to file HTTP basic auth credentials.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by elastic.

src cvelist · nday , bulk import · raw
{
  "id": 160748,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2016-10362",
  "occurred_at": "2017-06-16T21:00:00Z",
  "observed_at": "2026-11-13T05:36:29.933389Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2017-06-16T21:00:00.000Z",
    "assigner_short_name": "elastic"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.