Vulnerabilities (CVE)

Filtered by vendor Elastic Subscribe
Total 153 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2016-1000222 1 Elastic 1 Logstash 2024-11-21 5.0 MEDIUM 7.5 HIGH
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 1 Elastic 1 Logstash 2024-11-21 5.0 MEDIUM 7.5 HIGH
Logstash prior to version 2.3.4, Elasticsearch Output plugin would log to file HTTP authorization headers which could contain sensitive information.
CVE-2016-1000220 1 Elastic 1 Kibana 2024-11-21 4.3 MEDIUM 6.1 MEDIUM
Kibana before 4.5.4 and 4.1.11 are vulnerable to an XSS attack that would allow an attacker to execute arbitrary JavaScript in users' browsers.
CVE-2016-1000219 1 Elastic 1 Kibana 2024-11-21 5.0 MEDIUM 7.5 HIGH
Kibana before 4.5.4 and 4.1.11 when a custom output is configured for logging in, cookies and authorization headers could be written to the log files. This information could be used to hijack sessions of other users when using Kibana behind some form of authentication such as Shield.
CVE-2016-1000218 1 Elastic 1 Kibana Reporting 2024-11-21 6.8 MEDIUM 8.8 HIGH
Kibana Reporting plugin version 2.4.0 is vulnerable to a CSRF vulnerability that could allow an attacker to generate superfluous reports whenever an authenticated Kibana user navigates to a specially-crafted page.
CVE-2015-9056 1 Elastic 1 Kibana 2024-11-21 4.3 MEDIUM 6.1 MEDIUM
Kibana versions prior to 4.1.3 and 4.2.1 are vulnerable to a XSS attack.
CVE-2015-8131 1 Elastic 1 Kibana 2024-11-21 6.8 MEDIUM N/A
Cross-site request forgery (CSRF) vulnerability in Elasticsearch Kibana before 4.1.3 and 4.2.x before 4.2.1 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
CVE-2015-5619 2 Elastic, Elasticsearch 2 Logstash, Logstash 2024-11-21 4.3 MEDIUM 5.9 MEDIUM
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 2 Elastic, Elasticsearch 2 Logstash, Logstash 2024-11-21 5.0 MEDIUM 7.5 HIGH
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-2015-5377 1 Elastic 1 Elasticsearch 2024-11-21 7.5 HIGH 9.8 CRITICAL
Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol. NOTE: ZDI appears to claim that CVE-2015-3253 and CVE-2015-5377 are the same vulnerability
CVE-2015-4152 1 Elastic 1 Logstash 2024-11-21 6.4 MEDIUM N/A
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-2015-4093 1 Elastic 1 Kibana 2024-11-21 4.3 MEDIUM N/A
Cross-site scripting (XSS) vulnerability in Elasticsearch Kibana 4.x before 4.0.3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
CVE-2015-1427 2 Elastic, Redhat 2 Elasticsearch, Fuse 2024-11-21 7.5 HIGH 9.8 CRITICAL
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.
CVE-2014-4326 1 Elastic 1 Logstash 2024-11-21 7.5 HIGH N/A
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/.
CVE-2024-37280 1 Elastic 1 Elasticsearch 2024-10-03 N/A 4.9 MEDIUM
A flaw was discovered in Elasticsearch, affecting document ingestion when an index template contains a dynamic field mapping of “passthrough” type. Under certain circumstances, ingesting documents in this index would cause a StackOverflow exception to be thrown and ultimately lead to a Denial of Service. Note that passthrough fields is an experimental feature.
CVE-2024-37279 1 Elastic 1 Kibana 2024-10-03 N/A 4.3 MEDIUM
A flaw was discovered in Kibana, allowing view-only users of alerting to use the run_soon API making the alerting rule run continuously, potentially affecting the system availability if the alerting rule is running complex queries.
CVE-2024-37288 1 Elastic 1 Kibana 2024-09-16 N/A 8.8 HIGH
A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. This issue only affects users that use Elastic Security’s built-in AI tools https://www.elastic.co/guide/en/security/current/ai-for-security.html  and have configured an Amazon Bedrock connector https://www.elastic.co/guide/en/security/current/assistant-connect-to-bedrock.html .
CVE-2024-37286 1 Elastic 1 Apm Server 2024-09-11 N/A 6.5 MEDIUM
APM server logs contain document body from a partially failed bulk index request. For example, in case of unavailable_shards_exception for a specific document, since the ES response line contains the document body, and that APM server logs the ES response line on error, the document is effectively logged.
CVE-2023-49921 1 Elastic 1 Elasticsearch 2024-09-11 N/A 6.5 MEDIUM
An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level. This could lead to raw contents of documents stored in Elasticsearch to be printed in logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by removing this excessive logging. This issue only affects users that use Watcher and have a Watch defined that uses the search input and additionally have set the search input’s logger to DEBUG or finer, for example using: org.elasticsearch.xpack.watcher.input.search, org.elasticsearch.xpack.watcher.input, org.elasticsearch.xpack.watcher, or wider, since the loggers are hierarchical.
CVE-2024-37287 1 Elastic 1 Kibana 2024-08-22 N/A 7.2 HIGH
A flaw allowing arbitrary code execution was discovered in Kibana. An attacker with access to ML and Alerting connector features, as well as write access to internal ML indices can trigger a prototype pollution vulnerability, ultimately leading to arbitrary code execution.