Product:

Cortex\-A73_firmware

(Arm)
Repositories

Unknown:

This might be proprietary software.

#Vulnerabilities 5
Date Id Summary Products Score Patch Annotated
2023-01-10 CVE-2022-48251 The AES instructions on the ARMv8 platform do not have an algorithm that is "intrinsically resistant" to side-channel attacks. NOTE: the vendor reportedly offers the position "while power side channel attacks ... are possible, they are not directly caused by or related to the Arm architecture." Cortex\-A53_firmware, Cortex\-A55_firmware, Cortex\-A57_firmware, Cortex\-A72_firmware, Cortex\-A73_firmware, Cortex\-A75_firmware, Cortex\-A76_firmware, Cortex\-A76ae_firmware, Cortex\-A77_firmware, Cortex\-A78_firmware 7.5
2022-03-13 CVE-2022-23960 Certain Arm Cortex and Neoverse processors through 2022-03-08 do not properly restrict cache speculation, aka Spectre-BHB. An attacker can leverage the shared branch history in the Branch History Buffer (BHB) to influence mispredicted branches. Then, cache allocation can allow the attacker to obtain sensitive information. Cortex\-A57_firmware, Cortex\-A65_firmware, Cortex\-A65ae_firmware, Cortex\-A710_firmware, Cortex\-A72_firmware, Cortex\-A73_firmware, Cortex\-A75_firmware, Cortex\-A76_firmware, Cortex\-A76ae_firmware, Cortex\-A77_firmware, Cortex\-A78_firmware, Cortex\-A78ae_firmware, Cortex\-R7_firmware, Cortex\-R8_firmware, Cortex\-X1_firmware, Cortex\-X2_firmware, Neoverse\-E1_firmware, Neoverse\-V1_firmware, Neoverse_n1_firmware, Neoverse_n2_firmware, Debian_linux, Xen 5.6
2020-06-08 CVE-2020-13844 Arm Armv8-A core implementations utilizing speculative execution past unconditional changes in control flow may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka "straight-line speculation." Cortex\-A32_firmware, Cortex\-A34_firmware, Cortex\-A35_firmware, Cortex\-A53_firmware, Cortex\-A57_firmware, Cortex\-A72_firmware, Cortex\-A73_firmware, Leap 5.5
2022-03-10 CVE-2022-25368 Spectre BHB is a variant of Spectre-v2 in which malicious code uses the shared branch history (stored in the CPU BHB) to influence mispredicted branches in the victim's hardware context. Speculation caused by these mispredicted branches can then potentially be used to cause cache allocation, which can then be used to infer information that should be protected. Ampere_altra_firmware, Ampere_altra_max_firmware, Cortex\-A15_firmware, Cortex\-A57_firmware, Cortex\-A65_firmware, Cortex\-A65ae_firmware, Cortex\-A710_firmware, Cortex\-A72_firmware, Cortex\-A73_firmware, Cortex\-A75_firmware, Cortex\-A76_firmware, Cortex\-A76ae_firmware, Cortex\-A77_firmware, Cortex\-A78_firmware, Cortex\-A78ae_firmware, Cortex\-A78c_firmware, Cortex\-X1_firmware, Cortex\-X2_firmware, Neoverse\-E1_firmware, Neoverse\-V1_firmware, Neoverse_n1_firmware, Neoverse_n2_firmware 4.7