In Eclipse ThreadX before version 6.4.3, an attacker can cause a denial of service (crash) by providing a pointer to a reserved or unmapped memory region. Vulnerable system calls had a check of pointers, but that check wasn't verifying whether the pointer is outside the module memory region.
oryginał ENCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XEclipse Threadx
APPEclipse< 6.4.3
Powiązane podatności
The vulnerability stems from an incorrect error-checking logic in the CreateCounter() function (in threadx/uti...
In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't eno...
In Eclipse ThreadX before 6.4.0, xQueueCreate() and xQueueCreateSet() functions from the FreeRTOS compatibil...
In Eclipse ThreadX before version 6.4.0, the _Mtxinit() function in the Xtensa port was missing an array size...
In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases th...