org.elasticsearch:elasticsearch@8.19.22

  • latest version

    9.5.5

  • latest non vulnerable version

  • first published

    16 years ago

  • latest version published

    1 months ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

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

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Authorization Bypass Through User-Controlled Key

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

    Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the handling of cross-cluster search requests under the Remote Cluster Security (RCS) 2.0 model. An attacker can access unauthorized document contents, field mappings, metadata, and in limited cases modify retention lease states by sending a crafted request with mismatched shard identifiers, causing the authorization check to validate against an allowed index while accessing a different, unauthorized index. This is only exploitable if the attacker possesses a valid cross-cluster API key.

    How to fix Authorization Bypass Through User-Controlled Key?

    Upgrade org.elasticsearch:elasticsearch to version 8.19.23, 9.4.8, 9.5.5 or higher.

    [8.13.0,8.19.23)[9.0.0,9.4.8)[9.5.0,9.5.5)
    • H
    Allocation of Resources Without Limits or Throttling

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

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the retrieval process of multiple template resources with user-supplied metadata. An attacker can exhaust available heap memory and cause node failure by registering multiple resources within individual size limits and retrieving them together, resulting in out-of-memory errors.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade org.elasticsearch:elasticsearch to version 8.19.23, 9.4.7, 9.5.3 or higher.

    [8.0.0,8.19.23)[9.0.0,9.4.7)[9.5.0,9.5.3)
    • H
    Denial of Service (DoS)

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

    Affected versions of this package are vulnerable to Denial of Service (DoS) via the query processing engine. An attacker can cause uncontrolled memory growth by submitting specially crafted queries, leading to out-of-memory conditions and termination of nodes. This can be triggered repeatedly, including through queries embedded in shared resources, resulting in persistent cluster unavailability.

    How to fix Denial of Service (DoS)?

    Upgrade org.elasticsearch:elasticsearch to version 8.19.23, 9.4.8, 9.5.5 or higher.

    [8.0.0,8.19.23)[9.0.0,9.4.8)[9.5.0,9.5.5)
    • H
    Uncontrolled Recursion

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

    Affected versions of this package are vulnerable to Uncontrolled Recursion in the process that builds and serializes geometry values from scripted runtime fields. An attacker can cause the server to exhaust stack space and terminate by submitting a request with a script that generates a deeply nested structure. This is only exploitable if the attacker is an authenticated user with read access to at least one index.

    How to fix Uncontrolled Recursion?

    Upgrade org.elasticsearch:elasticsearch to version 8.19.23, 9.4.7, 9.5.5 or higher.

    [8.12.0,8.19.23)[9.0.0,9.4.7)[9.5.0,9.5.5)
    • H
    Memory Allocation with Excessive Size Value

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

    Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value via the description field. An attacker can exhaust available heap memory and crash the affected node by creating and accessing connector resources with excessively large values. This is only exploitable if the attacker is an authenticated user with connector management privileges.

    How to fix Memory Allocation with Excessive Size Value?

    Upgrade org.elasticsearch:elasticsearch to version 8.19.23, 9.4.8, 9.5.5 or higher.

    [8.12.0,8.19.23)[9.0.0,9.4.8)[9.5.0,9.5.5)