Buffer overflow in "rcardevinit" due to using due to using untrusted data (rcarimagenumber) as a loop counter before verifying it against RCARMAXBL3XIMAGE. This could lead to a full bypass of secure boot.

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in Renesas arm-trusted-firmware allows Local Execution of Code. This vulnerability is associated with program files https://github.Com/renesas-rcar/arm-trusted-firmware/blob/rcargen3v2.5/drivers/renesas/common/io/i... https://github.Com/renesas-rcar/arm-trusted-firmware/blob/rcargen3v2.5/drivers/renesas/common/io/iorcar.C .

In line 313 "addrloadedcnt" is checked not to be "CHECKIMAGEAREACNT" (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 "addrloadedcnt". This will allow an attacker to freely control the value of "addrloadedcnt" 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.

During the secure boot, bl2 (the second stage of the bootloader) loops over images defined in the table “bl2memparamsdescs”. For each image, the bl2 reads the image length and destination from the image’s certificate. Because of the way of reading from the image, which base on 32-bit unsigned integer value, it can result to an integer overflow. An attacker can bypass memory range restriction and write data out of buffer bounds, which could result in bypass of secure boot.

Affected git version from c2f286820471ed276c57e603762bd831873e5a17 until (not