Version 8.17.0

server

Elasticsearch subproject :server

Install Instructions

mvn install elasticsearch
Language Java

Find server vulnerabilities in your supply chain.

Scan for Free

server Vulnerabilities

Sort by
icon CVE (Latest)
  • icon CVE (Latest)
  • icon CVE (Oldest)
  • icon CVSS Score (Highest)
  • icon CVSS Score (Lowest)
CVE question mark icon CVSS Score question mark icon CWE(s) question mark icon EPSS Score question mark icon EPSS % question mark icon Impacted Versions
CVE-2014-3120 Medium 6.8 CWE-284 0.72582 0.98278
  • 1.0.0–1.1.2
  • 0.6.0–0.90.13
CVE-2014-6439 Medium 4.3 CWE-79 0.00253 0.64385
  • 1.0.0–1.3.9
  • 0.6.0–0.90.13
CVE-2015-1427 High 9.8 CWE-284 0.97188 0.99905
  • 1.0.0–1.4.2
  • 0.6.0–0.90.13
CVE-2015-3337 Medium 4.3 CWE-22 0.78606 0.98477
  • 1.0.0–1.5.1
  • 0.6.0–0.90.13
CVE-2015-4165 High 7.5 CWE-264, CWE-95 0.01179 0.84762
  • 1.0.0–1.5.2
  • 0.6.0–0.90.13
CVE-2015-5377 High 9.8 CWE-74, CWE-94 0.09845 0.94843
  • 1.0.0–1.6.0
  • 0.6.0–0.90.13
CVE-2015-5531 Medium 5 CWE-22 0.96825 0.99802
  • 1.0.0–1.6.0
  • 0.6.0–0.90.13
CVE-2018-3824 Medium 6.1 CWE-79 0.00085 0.37947
  • 6.0.0–6.2.3
  • 5.0.0–5.6.8
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2019-7611 High 8.1 CWE-275, CWE-284 0.00244 0.6362
  • 6.0.0–6.6.0
  • 5.0.0–5.6.14
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2019-7614 Medium 5.9 CWE-362 0.00168 0.54055
  • 7.0.0–7.2.0
  • 6.0.0–6.8.1
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2020-7019 Medium 6.5 CWE-270, CWE-269 0.00063 0.2915
  • 7.0.0–7.8.1
  • 6.0.0–6.8.11
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2020-7020 Low 3.1 CWE-270, CWE-269 0.00063 0.28913
  • 7.0.0–7.9.1
  • 6.0.0–6.8.12
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2020-7021 Medium 4.9 CWE-532 0.00063 0.2915
  • 7.0.0–7.9.3
  • 6.0.0–6.8.13
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2021-22135 Medium 5.3 CWE-200 0.00071 0.33011
  • 7.0.0–7.11.1
  • 6.0.0–6.8.14
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2021-22137 Medium 5.3 CWE-281, CWE-200 0.00071 0.33011
  • 7.0.0–7.11.1
  • 6.0.0–6.8.14
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2021-22144 Medium 6.5 CWE-674 0.00097 0.41667
  • 7.0.0–7.13.2
  • 6.0.0–6.8.16
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2023-31418 High 7.5 CWE-400 0.00126 0.47654
  • 8.0.0–8.8.2
  • 7.0.0–7.17.12
  • 6.0.0–6.8.23
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2023-49921 Medium 6.5 CWE-532 0.00049 0.20106
  • 8.0.0–8.11.1
  • 7.0.0–7.17.15
  • 6.0.0–6.8.23
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2024-23444 Medium 4.9 CWE-311 0.00043 0.10859
  • 8.0.0–8.12.2
  • 7.0.0–7.17.22
  • 6.0.0–6.8.23
  • 5.0.0–5.6.16
  • 2.0.0–2.4.6
  • 1.0.0–1.7.6
  • 0.6.0–0.90.13
CVE-2018-17244 Medium 6.5 CWE-200, CWE-362 0.00111 0.45084
  • 6.4.0–6.4.2
CVE-2019-7619 Medium 5.3 CWE-200, CWE-327 0.0026 0.64939
  • 7.0.0–7.3.2
  • 6.0.0–6.8.3
CVE-2018-3831 High 8.8 CWE-200 0.00077 0.35467
  • 6.0.0–6.4.0
  • 5.6.0–5.6.11
CVE-2018-3826 Medium 6.5 CWE-311, CWE-200 0.00064 0.30072
  • 6.0.0–6.2.4
CVE-2018-3827 High 8.1 CWE-532, CWE-255 0.00325 0.70433
  • 6.0.0–6.2.4
CVE-2020-7009 High 8.8 CWE-266, CWE-269 0.00137 0.49622
  • 7.0.0–7.6.1
  • 6.7.0–6.8.7
CVE-2020-7014 High 8.8 CWE-266, CWE-269 0.00104 0.43469
  • 7.0.0–7.6.1
  • 6.7.0–6.8.7
CVE-2023-31417 Medium 4.4 CWE-532 0.00045 0.1735
  • 8.0.0–8.9.1
  • 7.0.0–7.17.12
CVE-2023-31419 High 7.5 CWE-121, CWE-787 0.00206 0.58245
  • 8.0.0–8.9.0
  • 7.0.0–7.17.12
CVE-2023-46673 High 7.5 CWE-755 0.00078 0.35706
  • 8.0.0–8.10.2
  • 7.0.0–7.17.13
CVE-2024-23450 Medium 4.9 CWE-400 0.00045 0.1735
  • 8.0.0–8.12.2
  • 7.0.0–7.17.18
CVE-2018-17247 Medium 5.9 CWE-611 0.00222 0.59962
  • 6.5.0–6.5.1
CVE-2021-22147 Medium 6.5 CWE-732, CWE-862 0.00109 0.44601
  • 7.11.0–7.13.4
CVE-2021-22132 Medium 4.8 CWE-522 0.00082 0.36868
  • 7.7.0–7.10.1
CVE-2021-22134 Medium 4.3 CWE-863, CWE-200 0.00059 0.2678
  • 7.6.0–7.10.2
CVE-2024-23449 Medium 4.3 CWE-248 0.00043 0.10859
  • 8.4.0–8.11.0
CVE-2022-23712 High 7.5 CWE-754 0.00172 0.54499
  • 8.0.0–8.2.0
CVE-2022-23708 Medium 4.3 CWE-264, CWE-269 0.0005 0.21439
  • 7.16.0–7.17.0
CVE-2022-23710 Medium 6.1 CWE-79 0.00064 0.29768
  • 7.16.0–7.17.0
CVE-2024-12539 Unknown None None
  • 8.16.0–8.16.1
CVE-2024-23445 Medium 6.5 CWE-922, CWE-200 0.00043 0.10859
  • 8.10.1–8.13.4
CVE-2024-23451 Medium 4.4 CWE-863 0.00043 0.10859
  • 8.10.0–8.12.2
CVE-2024-37280 Medium 4.9 CWE-787, CWE-122 0.00044 0.15073
  • 8.13.1–8.13.4

server Vulnerability Remediation Guidance

CVE Description Full list of Impacted Versions Fix
CVE-2024-37280 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. 8.13.1, 8.13.4, 8.13.3, 8.13.2 Minor → 8.14.0
CVE-2024-23451 Incorrect Authorization issue exists in the API key based security model for Remote Cluster Security, which is currently in Beta, in Elasticsearch 8.10.0 and before 8.13.0. This allows a malicious user with a valid API key for a remote cluster configured to use the new Remote Cluster Security to read arbitrary documents from any index on the remote cluster, and only if they use the Elasticsearch custom transport protocol to issue requests with the target index ID, the shard ID and the document ID. None of Elasticsearch REST API endpoints are affected by this issue. 8.11.3, 8.11.0, 8.10.1, 8.11.2, 8.10.2, 8.10.4, 8.12.2, 8.12.1 (Show all) Minor → 8.14.0
CVE-2024-23450 A flaw was discovered in Elasticsearch, where processing a document in a deeply nested pipeline on an ingest node could cause the Elasticsearch node to crash. 7.3.0, 7.0.1, 7.2.1, 7.2.0, 7.1.1, 7.1.0, 7.0.0, 7.3.1 (Show all) Minor → 7.17.23
CVE-2024-23449 An uncaught exception in Elasticsearch >= 8.4.0 and < 8.11.1 occurs when an encrypted PDF is passed to an attachment processor through the REST API. The Elasticsearch ingest node that attempts to parse the PDF file will crash. This does not happen with password-protected PDF files or with unencrypted PDF files. 8.6.0, 8.4.2, 8.7.1, 8.7.0, 8.5.3, 8.4.1, 8.8.0, 8.6.2 (Show all) Minor → 8.14.0
CVE-2024-23445 It was identified that if a cross-cluster API key https://www.elastic.co/guide/en/elasticsearch/reference/8.14/security-api-create-cross-cluster-api-key.html#security-api-create-cross-cluster-api-key-request-body  restricts search for a given index using the query or the field_security parameter, and the same cross-cluster API key also grants replication for the same index, the search restrictions are not enforced during cross cluster search operations and search results may include documents and terms that should not be returned. This issue only affects the API key based security model for remote clusters https://www.elastic.co/guide/en/elasticsearch/reference/8.14/remote-clusters.html#remote-clusters-security-models  that was previously a beta feature and is released as GA with 8.14.0 8.11.3, 8.11.0, 8.10.1, 8.11.2, 8.13.1, 8.13.0, 8.10.2, 8.10.4 (Show all) Minor → 8.14.0
CVE-2024-23444 It was discovered by Elastic engineering that when elasticsearch-certutil CLI tool is used with the csr option in order to create a new Certificate Signing Requests, the associated private key that is generated is stored on disk unencrypted even if the --pass parameter is passed in the command invocation. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2024-12539 None 8.16.0, 8.16.1 Minor → 8.17.0
CVE-2023-49921 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. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2023-46673 It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when calling the Simulate Pipeline API. 7.3.0, 7.0.1, 7.2.1, 7.2.0, 7.1.1, 7.1.0, 7.0.0, 7.3.1 (Show all) Minor → 7.17.23
CVE-2023-31419 A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service. 7.3.0, 7.0.1, 7.2.1, 7.2.0, 7.1.1, 7.1.0, 7.0.0, 7.3.1 (Show all) Minor → 7.17.23
CVE-2023-31418 An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2023-31417 Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured. 7.3.0, 7.0.1, 7.2.1, 7.2.0, 7.1.1, 7.1.0, 7.0.0, 7.3.1 (Show all) Minor → 7.17.23
CVE-2022-23712 A Denial of Service flaw was discovered in Elasticsearch. Using this vulnerability, an unauthenticated attacker could forcibly shut down an Elasticsearch node with a specifically formatted network request. 8.2.0, 8.1.3, 8.1.2, 8.1.0, 8.1.1, 8.0.0, 8.0.1 Minor → 8.14.0
CVE-2022-23710 A cross-site-scripting (XSS) vulnerability was discovered in the Data Preview Pane (previously known as Index Pattern Preview Pane) which could allow arbitrary JavaScript to be executed in a victim’s browser. 7.16.3, 7.17.0, 7.16.1, 7.16.2, 7.16.0 Minor → 7.17.23
CVE-2022-23708 A flaw was discovered in Elasticsearch 7.17.0’s upgrade assistant, in which upgrading from version 6.x to 7.x would disable the in-built protections on the security index, allowing authenticated users with “*” index permissions access to this index. 7.16.3, 7.17.0, 7.16.1, 7.16.2, 7.16.0 Minor → 7.17.23
CVE-2021-22147 Elasticsearch before 7.14.0 did not apply document and field level security to searchable snapshots. This could lead to an authenticated user gaining access to information that they are unauthorized to view. 7.11.0, 7.11.1, 7.13.2, 7.12.1, 7.12.0, 7.13.3, 7.13.1, 7.13.0 (Show all) Minor → 7.17.23
CVE-2021-22144 In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2021-22137 In Elasticsearch versions before 7.11.2 and 6.8.15 a document disclosure flaw was found when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain cross-cluster search queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2021-22135 Elasticsearch versions before 7.11.2 and 6.8.15 contain a document disclosure flaw was found in the Elasticsearch suggester and profile API when Document and Field Level Security are enabled. The suggester and profile API are normally disabled for an index when document level security is enabled on the index. Certain queries are able to enable the profiler and suggester which could lead to disclosing the existence of documents and fields the attacker should not be able to view. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2021-22134 A document disclosure flaw was found in Elasticsearch versions after 7.6.0 and before 7.11.0 when Document or Field Level Security is used. Get requests do not properly apply security permissions when executing a query against a recently updated document. This affects documents that have been updated and not yet refreshed in the index. This could result in the search disclosing the existence of documents and fields the attacker should not be able to view. 7.10.1, 7.8.0, 7.10.2, 7.9.1, 7.9.0, 7.9.3, 7.6.1, 7.6.2 (Show all) Minor → 7.17.23
CVE-2021-22132 Elasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2 7.10.1, 7.8.0, 7.9.1, 7.9.0, 7.9.3, 7.8.1, 7.7.0, 7.9.2 (Show all) Minor → 7.17.23
CVE-2020-7021 Elasticsearch versions before 7.10.0 and 6.8.14 have an information disclosure issue when audit logging and the emit_request_body option is enabled. The Elasticsearch audit log could contain sensitive information such as password hashes or authentication tokens. This could allow an Elasticsearch administrator to view these details. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2020-7020 Elasticsearch versions before 6.8.13 and 7.9.2 contain a document disclosure flaw when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain complex queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2020-7019 In Elasticsearch before 7.9.0 and 6.8.12 a field disclosure flaw was found when running a scrolling search with Field Level Security. If a user runs the same query another more privileged user recently ran, the scrolling search can leak fields that should be hidden. This could result in an attacker gaining additional permissions against a restricted index. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2020-7014 The fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys and also authentication tokens. An attacker who is able to generate an API key and an authentication token can perform a series of steps that result in an authentication token being generated with elevated privileges. 7.3.0, 7.0.1, 6.8.2, 6.7.2, 6.8.0, 7.2.1, 6.7.1, 6.7.0 (Show all) Minor → 7.17.23
CVE-2020-7009 Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges. 7.3.0, 7.0.1, 6.8.2, 6.7.2, 6.8.0, 7.2.1, 6.7.1, 6.7.0 (Show all) Minor → 7.17.23
CVE-2019-7619 Elasticsearch versions 7.0.0-7.3.2 and 6.7.0-6.8.3 contain a username disclosure flaw was found in the API Key service. An unauthenticated attacker could send a specially crafted request and determine if a username exists in the Elasticsearch native realm. 6.4.2, 6.4.1, 6.4.0, 6.1.4, 6.6.1, 6.2.1, 6.2.0, 6.1.2 (Show all) Major → 7.17.23
CVE-2019-7614 A race condition flaw was found in the response headers Elasticsearch versions before 7.2.1 and 6.8.2 returns to a request. On a system with multiple users submitting requests, it could be possible for an attacker to gain access to response header containing sensitive data from another user. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2019-7611 A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are disabled and the _aliases, _shrink, or _split endpoints are used . If the elasticsearch.yml file has xpack.security.dls_fls.enabled set to false, certain permission checks are skipped when users perform one of the actions mentioned above, to make existing data available under a new index/alias name. This could result in an attacker gaining additional permissions against a restricted index. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2018-3831 Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This could allow an authenticated Elasticsearch user to improperly view these details. 6.4.0, 6.1.4, 6.2.1, 6.2.0, 6.1.2, 6.0.1, 6.1.1, 6.2.4 (Show all) Major → 7.17.23
CVE-2018-3827 A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged. 6.1.4, 6.2.1, 6.2.0, 6.1.2, 6.0.1, 6.1.1, 6.2.4, 6.1.0 (Show all) Major → 7.17.23
CVE-2018-3826 In Elasticsearch versions 6.0.0-beta1 to 6.2.4 a disclosure flaw was found in the _snapshot API. When the access_key and security_key parameters are set using the _snapshot API they can be exposed as plain text by users able to query the _snapshot API. 6.1.4, 6.2.1, 6.2.0, 6.1.2, 6.0.1, 6.1.1, 6.2.4, 6.1.0 (Show all) Major → 7.17.23
CVE-2018-3824 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. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2018-17247 Elasticsearch Security versions 6.5.0 and 6.5.1 contain an XXE flaw in Machine Learning's find_file_structure API. If a policy allowing external network access has been added to Elasticsearch's Java Security Manager then an attacker could send a specially crafted request capable of leaking content of local files on the Elasticsearch node. This could allow a user to access information that they should not have access to. 6.5.1, 6.5.0 Major → 7.17.23
CVE-2018-17244 Elasticsearch Security versions 6.4.0 to 6.4.2 contain an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. A request may receive headers intended for another request if the same username is being authenticated concurrently; when used with run as, this can result in the request running as the incorrect user. This could allow a user to access information that they should not have access to. 6.4.2, 6.4.1, 6.4.0 Major → 7.17.23
CVE-2015-5531 Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2015-5377 ** DISPUTED ** 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. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2015-4165 The snapshot API in Elasticsearch before 1.6.0 when another application exists on the system that can read Lucene files and execute code from them, is accessible by the attacker, and the Java VM on which Elasticsearch is running can write to a location that the other application can read and execute from, allows remote authenticated users to write to and create arbitrary snapshot metadata files, and potentially execute arbitrary code. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2015-3337 Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, allows remote attackers to read arbitrary files via unspecified vectors. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2015-1427 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. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2014-6439 Cross-site scripting (XSS) vulnerability in the CORS functionality in Elasticsearch before 1.4.0.Beta1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. 1.0.3, 0.90.1, 1.2.0, 1.2.3, 1.1.1, 1.1.0, 1.0.0, 1.2.1 (Show all) Major → 7.17.23
CVE-2014-3120 The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine. 1.0.3, 0.90.1, 1.1.1, 1.1.0, 1.0.0, 1.0.0.RC2, 1.0.0.Beta1, 0.90.13 (Show all) Major → 7.17.23

Instantly see if these server vulnerabilities affect your code.

Scan for Free

Dependencies

Packages using versions of server affected by its vulnerabilities

Dependent Packages
org.elasticsearch:elasticsearch-core:8.17.0
org.elasticsearch:elasticsearch-logging:8.17.0
org.elasticsearch:elasticsearch-secure-sm:8.17.0
org.elasticsearch:elasticsearch-x-content:8.17.0
org.elasticsearch:elasticsearch-geo:8.17.0
org.elasticsearch:elasticsearch-lz4:8.17.0
org.elasticsearch.plugin:elasticsearch-plugin-api:8.17.0
org.elasticsearch.plugin:elasticsearch-plugin-analysis-api:8.17.0
org.elasticsearch:elasticsearch-grok:8.17.0
org.elasticsearch:elasticsearch-tdigest:8.17.0
org.apache.lucene:lucene-core:9.12.0
org.apache.lucene:lucene-analysis-common:9.12.0
org.apache.lucene:lucene-backward-codecs:9.12.0
org.apache.lucene:lucene-facet:9.12.0
org.apache.lucene:lucene-grouping:9.12.0
org.apache.lucene:lucene-highlighter:9.12.0
org.apache.lucene:lucene-join:9.12.0
org.apache.lucene:lucene-memory:9.12.0
org.apache.lucene:lucene-misc:9.12.0
org.apache.lucene:lucene-queries:9.12.0
org.apache.lucene:lucene-queryparser:9.12.0
org.apache.lucene:lucene-sandbox:9.12.0
org.apache.lucene:lucene-suggest:9.12.0
org.elasticsearch:elasticsearch-cli:8.17.0
org.hdrhistogram:HdrHistogram:2.1.9
org.apache.logging.log4j:log4j-api:2.19.0
org.apache.logging.log4j:log4j-core:2.19.0
co.elastic.logging:log4j2-ecs-layout:1.2.0
co.elastic.logging:ecs-logging-core:1.2.0
org.elasticsearch:elasticsearch-simdvec:8.17.0
org.elasticsearch:elasticsearch-entitlement:8.17.0
com.carrotsearch:hppc:0.8.1
org.elasticsearch:elasticsearch-native:8.17.0