CVE-2019-7613
First published: Mon 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.
Credit: bressers@elastic.co bressers@elastic.co
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Elastic Winlogbeat | <5.6.16 | |
| Elastic Winlogbeat | >=6.0.0<6.6.2 | |
| <5.6.16 | ||
| >=6.0.0<6.6.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
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.
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.
What type of vulnerability is CVE-2019-7613?
CVE-2019-7613 is an insufficient logging vulnerability that allows attackers to manipulate log entries.
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.
- collector/nvd-index
- agent/type
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/description
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/author
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/tags
- agent/source
- vendor/elastic
- canonical/elastic winlogbeat
- version/elastic winlogbeat/6.0.0