Elasticsearch up to 7.17.20/8.13.2 allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Elasticsearch up to 7.17.20/8.13.2. This impacts an unknown function. Performing a manipulation results in allocation of resources. This vulnerability was named CVE-2024-43709. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Elasticsearch up to 7.17.20/8.13.2. This affects an unknown code. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:
An allocation of resources without limits or throttling in Elasticsearch can lead to an OutOfMemoryError exception resulting in a crash via a specially crafted query using an SQL function.
The advisory is shared at discuss.elastic.co. This vulnerability is uniquely identified as CVE-2024-43709 since 08/15/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 214589 (Elasticsearch 8.0.x < 8.13.3 / 7.17.21 (ESA-2024-25)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 7.17.21 or 8.13.3 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (214589). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 7.17.0
- 7.17.1
- 7.17.2
- 7.17.3
- 7.17.4
- 7.17.5
- 7.17.6
- 7.17.7
- 7.17.8
- 7.17.9
- 7.17.10
- 7.17.11
- 7.17.12
- 7.17.13
- 7.17.14
- 7.17.15
- 7.17.16
- 7.17.17
- 7.17.18
- 7.17.19
- 7.17.20
- 8.13.0
- 8.13.1
- 8.13.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 6.5
CNA Vector (elastic): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 214589
Nessus Name: Elasticsearch 8.0.x < 8.13.3 / 7.17.21 (ESA-2024-25)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Elasticsearch 7.17.21/8.13.3
Timeline
08/15/2024 🔍01/21/2025 🔍
01/21/2025 🔍
02/01/2025 🔍
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2024-43709 (🔍)
GCVE (CVE): GCVE-0-2024-43709
GCVE (VulDB): GCVE-100-292653
Entry
Created: 01/21/2025 13:06Updated: 02/01/2025 06:25
Changes: 01/21/2025 13:06 (29), 01/21/2025 13:09 (33), 01/21/2025 15:22 (1), 01/21/2025 15:37 (2), 01/25/2025 05:31 (2), 02/01/2025 06:25 (11)
Complete: 🔍
Committer: sany
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Interested in the pricing of exploits?
See the underground prices here!