CVE-2018-3817 Information disclosure in Logstash
Medium 6.5
Published
Updated
Check this codebase for CVE-2018-3817 and fix it if it is affected.
What it is: CVE-2018-3817 is a medium-severity vulnerability in Elastic Logstash, published on 30 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3817 in the wild and no public exploit code.
Affected product: Elastic Logstash. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2018-3817/ (Markdown: https://insights.sbomify.com/CVE-2018-3817/index.md)
Attackers can access sensitive information logged by Logstash when it processes deprecated settings, requiring an upgrade to secure data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2018-3817?
CVE-2018-3817 is a medium-severity vulnerability in Elastic Logstash, published on 30 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive information.
Which versions are affected by CVE-2018-3817?
It affects 1 product.
Products include Elastic Logstash.
How do I fix CVE-2018-3817?
Upgrade to a fixed version.
Is CVE-2018-3817 being exploited?
There is no known exploitation of CVE-2018-3817 in the wild and no public exploit code.
Other vulnerabilities in Elastic Logstash
- CVE-2019-7612 Information disclosure in Logstash
- CVE-2023-46672 Logstash Insertion of Sensitive Information into Log File
- CVE-2026-33466 Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write
- CVE-2019-7620 Denial of service in Logstash
- CVE-2015-5378 Information disclosure in n/a
Sources
Also known as GHSA-m5wv-852x-cj2g.