CVE-2019-7613: High severity elastic vulnerability
Published Mar 25, 2019
·Updated
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.
Affected Software
2 affected components
Elastic Winlogbeat<5.6.16
Elastic Winlogbeat>=6.0.0<6.6.2
Event History
Mar 25, 2019
CVE Published
via MITRE·06:34 PM
Data Sourced
via MITRE·06:34 PM
DescriptionWeakness
Data Sourced
via NVD·07:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-7613?
CVE-2019-7613 has been classified as a medium severity vulnerability due to its potential impact on logging integrity.
2
How can I fix CVE-2019-7613?
To fix CVE-2019-7613, upgrade Winlogbeat to version 5.6.16 or 6.6.2 or later.
3
What versions of Winlogbeat are affected by CVE-2019-7613?
Winlogbeat versions prior to 5.6.16 and between 6.0.0 and 6.6.2 are affected by CVE-2019-7613.
4
What type of vulnerability is CVE-2019-7613?
CVE-2019-7613 is an insufficient logging vulnerability that allows attackers to manipulate log entries.
5
Why is CVE-2019-7613 a concern for organizations?
CVE-2019-7613 is a concern for organizations because it can lead to loss of forensic data, complicating incident response efforts.