Overview 18 matches · 2 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
18matches
2in Waratek scope11.1%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
11.1%
Outside Waratek scope
0
0.0%
Not applicable
16
88.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
18
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
18
100.0%
split by
peak 6 / year
20141
Not applicable1
High1
not blocked1
No public exploit1
20151
Not applicable1
Medium1
not blocked1
No public exploit1
20160
20176
Not applicable6
High5
Medium1
not blocked6
No public exploit6
20183
No exploit published1
Not applicable2
Medium3
not blocked3
No public exploit3
20192
Not applicable2
Critical1
High1
not blocked2
No public exploit2
20201
No exploit published1
Medium1
not blocked1
No public exploit1
20211
Not applicable1
Low1
not blocked1
No public exploit1
20221
Not applicable1
Critical1
not blocked1
No public exploit1
20231
Not applicable1
High1
not blocked1
No public exploit1
20240
20250
20261
Not applicable1
Critical1
not blocked1
No public exploit1
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-33466 | Critical | 2026-04-08 | Not applicable | No public exploit | Improper Limitation of a Pathname to a Restricted Directory (CWE-22) in Logstash can lead to arbitrary file write and potentially remote code execution via Relative Path Traversal (CAPEC-139). The archive extraction utilities used by Logstash do not properly validate file paths within compressed archives. An attacker who can serve a specially crafted archive to Logstash through a compromised or attacker-controlled update endpoint can write arbitrary files to the host filesystem with the privileges of the Logstash process. In certain configurations where automatic pipeline reloading is enabled, this can be escalated to remote code execution. |
| CVE-2023-46672 | High | 2023-11-15 | Not applicable | No public exploit | An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances. The prerequisites for the manifestation of this issue are: * Logstash is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format. * Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration. |
| CVE-2022-31520 | Critical | 2022-07-11 | Not applicable | No public exploit | The Luxas98/logstash-management-api repository through 2020-05-04 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely. |
| CVE-2021-22138 | Low | 2021-05-13 | Not applicable | No public exploit | In Logstash versions after 6.4.0 and before 6.8.15 and 7.12.0 a TLS certificate validation flaw was found in the monitoring feature. When specifying a trusted server CA certificate Logstash would not properly verify the certificate returned by the monitoring server. This could result in a man in the middle style attack against the Logstash monitoring data. |
| CVE-2020-2143 | Medium | 2020-03-09 | No exploit published | No public exploit | Jenkins Logstash Plugin 2.3.1 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure. |
| CVE-2019-7620 | High | 2019-10-30 | Not applicable | No public exploit | Logstash versions before 7.4.1 and 6.8.4 contain a denial of service flaw in the Logstash Beats input plugin. An unauthenticated user who is able to connect to the port the Logstash beats input could send a specially crafted network packet that would cause Logstash to stop responding. |
| CVE-2019-7612 | Critical | 2019-03-25 | Not applicable | No public exploit | A sensitive data disclosure flaw was found in the way Logstash versions before 5.6.15 and 6.6.1 logs malformed URLs. If a malformed URL is specified as part of the Logstash configuration, the credentials for the URL could be inadvertently logged as part of the error message. |
| CVE-2018-3824 | Medium | 2018-09-19 | No exploit published | No public exploit | X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. If an attacker is able to inject data into an index that has a ML job running against it, then when another user views the results of the ML job it could allow the attacker to obtain sensitive information from or perform destructive actions on behalf of that other ML user. |
| CVE-2018-3823 | Medium | 2018-09-19 | Not applicable | No public exploit | X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. Users with manage_ml permissions could create jobs containing malicious data as part of their configuration that could allow the attacker to obtain sensitive information from or perform destructive actions on behalf of other ML users viewing the results of the jobs. |
| CVE-2018-3817 | Medium | 2018-03-30 | Not applicable | No public exploit | When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive information. |
| CVE-2017-14730 | High | 2017-09-25 | Not applicable | No public exploit | The init script in the Gentoo app-admin/logstash-bin package before 5.5.3 and 5.6.x before 5.6.1 has "chown -R" calls for user-writable directory trees, which allows local users to gain privileges by leveraging access to a $LS_USER account for creation of a hard link. |
| CVE-2015-5619 | Medium | 2017-08-09 | Not applicable | No public exploit | Logstash 1.4.x before 1.4.5 and 1.5.x before 1.5.4 with Lumberjack output or the Logstash forwarder does not validate SSL/TLS certificates from the Logstash server, which might allow attackers to obtain sensitive information via a man-in-the-middle attack. |
| CVE-2015-5378 | High | 2017-06-27 | Not applicable | No public exploit | Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read communications between Logstash Forwarder agent and Logstash server. |
| CVE-2016-10363 | High | 2017-06-16 | Not applicable | No public exploit | Logstash versions prior to 2.3.3, when using the Netflow Codec plugin, a remote attacker crafting malicious Netflow v5, Netflow v9 or IPFIX packets could perform a denial of service attack on the Logstash instance. The errors resulting from these crafted inputs are not handled by the codec and can cause the Logstash process to exit. |
| CVE-2016-1000222 | High | 2017-06-16 | Not applicable | No public exploit | Logstash prior to version 2.1.2, the CSV output can be attacked via engineered input that will create malicious formulas in the CSV data. |
| CVE-2016-1000221 | High | 2017-06-16 | Not applicable | No public exploit | Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive information. |
| CVE-2015-4152 | Medium | 2015-06-15 | Not applicable | No public exploit | Directory traversal vulnerability in the file output plugin in Elasticsearch Logstash before 1.4.3 allows remote attackers to write to arbitrary files via vectors related to dynamic field references in the path option. |
| CVE-2014-4326 | High | 2014-07-22 | Not applicable | No public exploit | Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/. |