CVE-2019-7613 Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw.
High 7.5
Published
Updated
Check this codebase for CVE-2019-7613 and fix it if it is affected.
What it is: CVE-2019-7613 is a high-severity vulnerability in Elastic Logstash, published on 25 Mar 2019.
Exploitation: There is no known exploitation of CVE-2019-7613 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-2019-7613/ (Markdown: https://insights.sbomify.com/CVE-2019-7613/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2019-7613?
CVE-2019-7613 is a high-severity vulnerability in Elastic Logstash, published on 25 Mar 2019.
Official description
Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw. An attacker able to inject certain characters into a log entry could prevent Winlogbeat from recording the event.
Weakness: CWE-778
Which versions are affected by CVE-2019-7613?
It affects 1 product.
Products include Elastic Winlogbeat.
How do I fix CVE-2019-7613?
No fix has been published for CVE-2019-7613 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-7613 being exploited?
There is no known exploitation of CVE-2019-7613 in the wild and no public exploit code.
Other vulnerabilities in Elastic Logstash
Sources
Also known as GHSA-2mc6-hfwx-q7vw.