CVE-2019-7613 json
Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw.
published 7y ago modified 4mo ago also EUVD-2019-17150
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- elastic winlogbeat 5.6.16, 6.6.2
Is CVE-2019-7613 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- Elastic Logstash
Classification
- Weakness
-
- CWE-778 Insufficient Logging
References
-
elastic.co
/community/security
vendor-advisory
-
discuss.elastic.co
/t/elastic-stack-6-6-2-and-5-6-16-security-update/173180
vendor-advisory
Sources
- CVE List CVE-2019-7613
- NVD CVE-2019-7613
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.