org.elasticsearch:elasticsearch@8.11.0 vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the org.elasticsearch:elasticsearch package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Incorrect Authorization

org.elasticsearch:elasticsearch is a Distributed, RESTful Search Engine.

Affected versions of this package are vulnerable to Incorrect Authorization in the API-key-based security model for Remote Cluster Security (in beta). This allows a malicious user with a valid API key for a remote cluster configured to use Remote Cluster Security to read arbitrary documents from any index on the remote cluster, using the Elasticsearch custom transport protocol to issue requests with the target index ID, the shard ID, and the document ID.

Note:

None of the Elasticsearch REST API endpoints are affected by this issue.

How to fix Incorrect Authorization?

Upgrade org.elasticsearch:elasticsearch to version 8.13.0 or higher.

[8.10.0,8.13.0)
  • M
Uncontrolled Recursion

org.elasticsearch:elasticsearch is a Distributed, RESTful Search Engine.

Affected versions of this package are vulnerable to Uncontrolled Recursion when processing a document in a deeply nested pipeline on an ingest node, causing the node to crash.

How to fix Uncontrolled Recursion?

Upgrade org.elasticsearch:elasticsearch to version 7.17.19, 8.13.0 or higher.

[,7.17.19) [8.0.0-alpha1,8.13.0)
  • M
Insertion of Sensitive Information into Log File

org.elasticsearch:elasticsearch is a Distributed, RESTful Search Engine.

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to the logging of Watcher search input at the DEBUG log level, which may result in the unintended recording of sensitive information in log files. An attacker can gain access to sensitive data by examining the log files that contain the search query results.

Note:

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.

How to fix Insertion of Sensitive Information into Log File?

Upgrade org.elasticsearch:elasticsearch to version 7.17.16, 8.11.2 or higher.

[7.0.0,7.17.16) [8.0.0,8.11.2)