Eclipse ThreadX up to 6.3.x tx_freertos.c xQueueCreate/xQueueCreateSet heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Eclipse ThreadX up to 6.3.x. It has been rated as critical. Affected by this vulnerability is the function xQueueCreate/xQueueCreateSet of the file utility/rtos_compatibility_layers/FreeRTOS/tx_freertos.c. Performing a manipulation results in heap-based overflow.
This vulnerability is reported as CVE-2024-2212. The attack requires a local approach. Moreover, an exploit is present.
Upgrading the affected component is advised.
Details
A vulnerability was found in Eclipse ThreadX up to 6.3.x. It has been classified as critical. This affects the function xQueueCreate/xQueueCreateSet of the file utility/rtos_compatibility_layers/FreeRTOS/tx_freertos.c. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Eclipse ThreadX before 6.4.0, xQueueCreate() and xQueueCreateSet() functions from the FreeRTOS compatibility API (utility/rtos_compatibility_layers/FreeRTOS/tx_freertos.c) were missing parameter checks. This could lead to integer wraparound, under-allocations and heap buffer overflows.
The weakness was disclosed by Marco Ivaldi. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-2212 since 03/06/2024. The exploitability is told to be easy. Attacking locally is a requirement. Technical details and a public exploit are known.
The exploit is shared for download at packetstormsecurity.com. It is declared as proof-of-concept.
Upgrading to version 6.4.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 7.3
CNA Vector (Eclipse Foundation): 🔍
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: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ThreadX 6.4.0
Timeline
03/06/2024 🔍03/26/2024 🔍
03/26/2024 🔍
02/07/2025 🔍
Sources
Advisory: GHSA-v9jj-7qjg-h6g6Researcher: Marco Ivaldi
Status: Confirmed
CVE: CVE-2024-2212 (🔍)
GCVE (CVE): GCVE-0-2024-2212
GCVE (VulDB): GCVE-100-258027
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/26/2024 17:20Updated: 02/07/2025 00:09
Changes: 03/26/2024 17:20 (65), 05/05/2024 08:40 (1), 05/05/2024 08:41 (1), 06/03/2024 11:02 (10), 06/11/2024 13:23 (1), 02/07/2025 00:09 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.