Output PluginPlugin / extension · Elasticsearch
CVE-2016-10362
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPrior to Logstash version 5.0.1, Elasticsearch Output plugin when updating connections after sniffing, would log to file HTTP basic auth credentials.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Elasticsearch Output plugin in Logstash versions prior to 5.0.1 had a vulnerability where HTTP basic authentication credentials were being written to log files in plaintext when the plugin performed connection updates after sniffing for Elasticsearch nodes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Output PluginPlugin / extension
<= 5.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Elasticsearch Output Plugin versionRun 'logstash-plugin list | grep logstash-output-elasticsearch' or check the plugin .gem file in the Logstash vendor directory to determine the installed version of the Elasticsearch Output plugin.Affected if The installed version is 5.0.0 or earlier.
-
Verify HTTP basic authentication is configuredExamine the Logstash pipeline configuration file (usually in /etc/logstash/conf.d/ or specified via -f flag) for the elasticsearch output block. Look for 'user' and 'password' parameters, or 'cloud_auth' parameter that contains credentials.Affected if HTTP basic authentication credentials (user/password or cloud_auth) are configured in the Elasticsearch Output plugin settings.
-
Inspect Logstash log files for plaintext credentialsSearch Logstash log files (typically located in /var/log/logstash/ or the LOGS_DIR specified in logstash.yml) for occurrences of the configured username or password in plaintext. Use grep to search for the username or password strings.Affected if The username or password from the Elasticsearch Output configuration appears in plaintext within Logstash log files.
A system is affected if the Elasticsearch Output Plugin version is 5.0.0 or earlier AND HTTP basic authentication is configured, which may have resulted in credentials being written to log files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Logstash version 5.0.1 or later to receive the patched Elasticsearch Output plugin that no longer logs credentials.
Fix this in Output Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data