CVE-2024-23562
Lun, 08/07/2024 – 16:15
CVE-2024-23562
CVE-2024-23562
Lun, 08/07/2024 – 16:15
CVE-2024-23562
CVE-2024-21778
Lun, 08/07/2024 – 16:15
CVE-2024-21778
CVE-2023-50383
Lun, 08/07/2024 – 16:15
CVE-2023-50383
CVE-2024-39699
Lun, 08/07/2024 – 16:15
CVE-2024-39699
CVE-2024-39695
Lun, 08/07/2024 – 16:15
CVE-2024-39695
CVE-2024-39203
Lun, 08/07/2024 – 16:15
CVE-2024-39203
CVE-2024-39202
Lun, 08/07/2024 – 16:15
CVE-2024-39202
CVE-2024-31504
Lun, 08/07/2024 – 16:15
CVE-2024-31504
CVE-2024-6564
Lun, 08/07/2024 – 16:15
CVE-2024-6564
CVE-2024-6563
Lun, 08/07/2024 – 16:15
CVE-2024-6563
In line 313 "addr_loaded_cnt" is checked not to be "CHECK_IMAGE_AREA_CNT" (5) or larger, this check does not halt the function. Immediately after (line 317) there will be an overflow in the buffer and the value of "dst" will be written to the area immediately after the buffer, which is "addr_loaded_cnt". This will allow an attacker to freely control the value of "addr_loaded_cnt" and thus control the destination of the write immediately after (line 318). The write in line 318 will then be fully controlled by said attacker, with whichever address and whichever value ("len") they desire.