Ingest-node crash via uncaught PDF parser error
Published Mar 29, 2024 · Updated Aug 12, 2024
Uncaught exception in Elasticsearch 8.4.0 through 8.11.0 allows remote authenticated users to crash an ingest node via an encrypted PDF. TikaImpl.parse leaves a Bouncy Castle LinkageError from public-key-encrypted PDFs uncaught, allowing it to escape attachment processing and terminate the node. The REST request requires low-privilege authentication and a configured attachment pipeline; password-encrypted and unencrypted PDFs do not trigger the crash.
Summary
What happened
Uncaught exception in Elasticsearch 8.4.0 through 8.11.0 allows remote authenticated users to crash an ingest node via an encrypted PDF. TikaImpl.parse leaves a Bouncy Castle LinkageError from public-key-encrypted PDFs uncaught, allowing it to escape attachment processing and terminate the node. The REST request requires low-privilege authentication and a configured attachment pipeline; password-encrypted and unencrypted PDFs do not trigger the crash.
The record
- CVE
- CVE-2024-23449
- Published
- Mar 29, 2024
- Updated
- Aug 12, 2024
- Vendor
- Elastic
- Product
- Elasticsearch
- Classifications
- CWE-248, CAPEC-100, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.4.0 <8.11.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo