p PatchFirst

PatchFirst · Latest vulnerabilities

elasticsearch vulnerabilities · Page 2

Vulnerabilities published for elasticsearch in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 41

  1. CVE-2021-37937

    Medium · CVSS 5.9EPSS 0.71%No fix published

    Elasticsearch privilege escalation

    An issue was found with how API keys are created with the Fleet-Server service account. When an API key is created with a service account, it is possible that the API key could be created with higher privileges than intended. Using this vulnerability, a compromised Fleet-Server service account could escalate themselves to a super-user.

    Published Updated
  2. CVE-2023-31417

    Medium · CVSS 4.1EPSS 0.24%No fix published

    Elasticsearch Insertion of sensitive information in audit logs

    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.

    Published Updated
  3. CVE-2023-31418

    High · CVSS 7.5EPSS 2.05%No fix published

    Elasticsearch uncontrolled resource consumption

    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.

    Published Updated
  4. CVE-2021-22144

    Medium · CVSS 6.5EPSS 2.44%No fix published

    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.

    Published Updated
  5. CVE-2021-22145

    Medium · CVSS 6.5EPSS 76.25%Public exploitNo fix published

    CVE-2021-22145

    A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting. A user with the ability to submit arbitrary queries to Elasticsearch could submit a malformed query that would result in an error message returned containing previously used portions of a data buffer. This buffer could contain sensitive information such as Elasticsearch documents or authentication details.

    Published Updated
  6. CVE-2021-22137

    Medium · CVSS 5.3EPSS 1.19%No fix published

    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.

    Published Updated
  7. CVE-2021-22135

    Medium · CVSS 5.3EPSS 1.34%No fix published

    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.

    Published Updated
  8. CVE-2021-22134

    Medium · CVSS 4.3EPSS 1.11%No fix published

    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.

    Published Updated
  9. CVE-2020-7021

    Medium · CVSS 4.9EPSS 1.47%No fix published

    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.

    Published Updated
  10. CVE-2021-22132

    Medium · CVSS 4.8EPSS 1.22%No fix published

    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

    Published Updated
  11. CVE-2020-7020

    Low · CVSS 3.1EPSS 1.08%No fix published

    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.

    Published Updated
  12. CVE-2020-7019

    Medium · CVSS 6.5EPSS 1.4%No fix published

    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.

    Published Updated
  13. CVE-2020-7018

    High · CVSS 8.8EPSS 1.09%No fix published

    CVE-2020-7018

    Elastic Enterprise Search before 7.9.0 contain a credential exposure flaw in the App Search interface. If a user is given the �developer� role, they will be able to view the administrator API credentials. These credentials could allow the developer user to conduct operations with the same permissions of the App Search administrator.

    Published Updated
  14. CVE-2020-7014

    High · CVSS 8.8EPSS 1.74%No fix published

    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.

    Published Updated
  15. CVE-2020-7011

    Medium · CVSS 6.1EPSS 1.01%No fix published

    CVE-2020-7011

    Elastic App Search versions before 7.7.0 contain a cross site scripting (XSS) flaw when displaying document URLs in the Reference UI. If the Reference UI injects a URL into a result, that URL will be rendered by the web browser. If an attacker is able to control the contents of such a field, they could execute arbitrary JavaScript in the victim�s web browser.

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →