Skip to content

GHSA-pw39-f3m5-cxfc BIT-elasticsearch-2024-23449 CVE-2024-23449

Elasticsearch Uncaught Exception leading to crash

Medium Maven
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.68%
Chance of exploitation in the next 30 days. Higher than 52.47% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-248 Uncaught Exception
Fix
8.11.1
Upgrade org.elasticsearch:elasticsearch to this version or later

Description

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.

Affected versions

Maven

PackageVulnerableFixed in
org.elasticsearch:elasticsearch
>= 8.4.0, < 8.11.1
8.11.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.elasticsearch:elasticsearch Maven → 8.11.1

maven
<dependency><groupId>org.elasticsearch</groupId><artifactId>elasticsearch</artifactId><version>8.11.1</version></dependency>
gradle
implementation("org.elasticsearch:elasticsearch:8.11.1")

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Weakness

CWE-248: Uncaught Exception

An exception is thrown from a function, but it is not caught.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mrfm-jxgf-2h6v
Elasticsearch Improper Access Control vulnerability
High Known exploited Also affects org.elasticsearch:elasticsearch
GHSA-w94p-6mhw-4qxw
Improper Access Control in Elasticsearch
High Known exploited Also affects org.elasticsearch:elasticsearch
GHSA-mm3m-5497-xggg
Elasticsearch Uncontrolled Resource Consumption Vulnerability
High Also affects org.elasticsearch:elasticsearch
GHSA-5xm9-x7x4-4j5x
Elasticsearch Vulnerable to Stack Overflow due to a Large Recursion
High Also affects org.elasticsearch:elasticsearch
GHSA-jgx4-7v3v-vwfm
Elasticsearch allocation of resources without limits or throttling leads to crash
High Also affects org.elasticsearch:elasticsearch
GHSA-5mpw-4546-2wcr
Elasticsearch Incorrect Authorization vulnerability
Medium Also affects org.elasticsearch:elasticsearch
GHSA-5v8f-xx9m-wj44
Elasticsearch stores private key on disk unencrypted
High Also affects org.elasticsearch:elasticsearch
GHSA-2hjr-vmf3-xwvp
Elasticsearch Insertion of Sensitive Information into Log File
Medium Also affects org.elasticsearch:elasticsearch
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor