CVE-2016-10362 — Vulnerability in logstash-core — CVE Details
Logstash Logs Sensitive Information
Summary
Advisory Timeline
- First published May 13, 2022 (1613 days ago).
- Last revised February 16, 2024 — 644 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
gem install logstash-core -v 5.0.1
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: rubygems (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| logstash-core | rubygems | 1.5.0, 1.5.0.beta2, 1.5.0.rc1, 1.5.0.rc1.1 (+102 more) | 5.0.1 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-200Information ExposureMITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 6.5 score means for each attack dimension.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
References
Frequently Asked Questions
- What is CVE-2016-10362?
- Logstash Logs Sensitive Information This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.5/10).
- How do I check if my project is affected by CVE-2016-10362?
- CVE-2016-10362 affects logstash-core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2016-10362 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation requires specific conditions or has limited impact. Remediate within weeks.
Also Known As
Related CVEs
- CVE-2016-1000221HIGH
Logstash Logs Sensitive Information
- CVE-2026-107715MEDIUM
Mechanize sends credential headers to another host after an HTTP redirect
- CVE-2026-107399MEDIUM
Mechanize sends credential headers to another origin after a meta refresh
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies