← Back

Trustedfirmware

trustedfirmware

84 CVEs • 5 products

Products (5)

Click to collapse
Toggle
Mbed Tls
mbed_tls
Op Tee
op-tee
Tf Psa Crypto
tf-psa-crypto

CVEs (84)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
3Linaro
TrustedfirmwareWesterndigital
5Inand Cl Em132 Firmware
Inand Ix Em132 FirmwareInand Ix Em132 Xi Firmware+2 more
Jun 17, 2026
Nov 18, 2020
N/A· v4
6.8 MEDIUM· v3
4.6 MEDIUM· v2
Western Digital has identified a security vulnerability in the Replay Protected Memory Block (RPMB) protocol as specified in multiple standards for storage device interfaces, including all versions of eMMC, UFS, and NVMe...Show more
Western Digital has identified a security vulnerability in the Replay Protected Memory Block (RPMB) protocol as specified in multiple standards for storage device interfaces, including all versions of eMMC, UFS, and NVMe. The RPMB protocol is specified by industry standards bodies and is implemented by storage devices from multiple vendors to assist host systems in securing trusted firmware. Several scenarios have been identified in which the RPMB state may be affected by an attacker without the knowledge of the trusted component that uses the RPMB feature.Show less
4Arm
DebianFedoraproject+1 more
4Debian Linux
FedoraMbed Tls+1 more
Jun 17, 2026
Apr 15, 2020
N/A· v4
4.7 MEDIUM· v3
1.9 LOW· v2
An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15. An attacker that can get precise enough side-channel measurements can recover the long-term ECDSA private key by (1) reconstructing the proje...Show more
An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15. An attacker that can get precise enough side-channel measurements can recover the long-term ECDSA private key by (1) reconstructing the projective coordinate of the result of scalar multiplication by exploiting side channels in the conversion to affine coordinates; (2) using an attack described by Naccache, Smart, and Stern in 2003 to recover a few bits of the ephemeral scalar from those projective coordinates via several measurements; and (3) using a lattice attack to get from there to the long-term ECDSA private key used for the signatures. Typically an attacker would have sufficient access when attacking an SGX enclave and controlling the untrusted OS.Show less
4Arm
DebianFedoraproject+1 more
5Debian Linux
FedoraMbed Crypto+2 more
Jun 17, 2026
Sep 26, 2019
N/A· v4
5.3 MEDIUM· v3
2.6 LOW· v2
Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel...Show more
Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel attacks if a victim signs the same message many times. (For Mbed TLS, the fix is also available in versions 2.7.12 and 2.16.3.)Show less
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 16, 2019
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Linaro/OP-TEE OP-TEE Prior to version v3.4.0 is affected by: Boundary checks. The impact is: This could lead to corruption of any memory which the TA can access. The component is: optee_os. The fixed version is: v3.4.0.
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
9.8 CRITICAL· v3
10.0 HIGH· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow. The impact is: Code execution in the context of TEE core (kernel). The component is: optee_os. The fixed version is: 3.4.0 and later.
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
9.8 CRITICAL· v3
10.0 HIGH· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow. The impact is: Execution of code in TEE core (kernel) context. The component is: optee_os. The fixed version is: 3.4.0 and later.
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
9.8 CRITICAL· v3
10.0 HIGH· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow. The impact is: Code execution in context of TEE core (kernel). The component is: optee_os. The fixed version is: 3.4.0 and later.
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow. The impact is: Memory corruption and disclosure of memory content. The component is: optee_os. The fixed version is: 3.4.0 and later.
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Rounding error. The impact is: Potentially leaking code and/or data from previous Trusted Application. The component is: optee_os. The fixed version is: 3.4.0 and la...Show more
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Rounding error. The impact is: Potentially leaking code and/or data from previous Trusted Application. The component is: optee_os. The fixed version is: 3.4.0 and later.Show less
2Linaro
Trustedfirmware
2Op Tee
Op Tee
Jun 17, 2026
Jul 15, 2019
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Boundary crossing. The impact is: Memory corruption of the TEE itself. The component is: optee_os. The fixed version is: 3.4.0 and later.
2Arm
Trustedfirmware
2Trusted Firmware A
Trusted Firmware A
Jun 5, 2026
Jan 30, 2019
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
ARM Trusted Firmware-A allows information disclosure.
2Arm
Trustedfirmware
2Arm Trusted Firmware
Trusted Firmware A
Jun 5, 2026
Dec 18, 2018
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
In all versions of ARM Trusted Firmware up to and including v1.4, not initializing or saving/restoring the PMCR_EL0 register can leak secure world timing information.
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 5, 2026
Dec 5, 2018
N/A· v4
4.7 MEDIUM· v3
1.9 LOW· v2
Arm Mbed TLS before 2.14.1, before 2.7.8, and before 2.1.17 allows a local unprivileged attacker to recover the plaintext of RSA decryption, which is used in RSA-without-(EC)DH(E) cipher suites.
3Libtom
LinaroTrustedfirmware
3Libtomcrypt
Op TeeOp Tee
Jun 5, 2026
Jun 15, 2018
N/A· v4
4.9 MEDIUM· v3
1.9 LOW· v2
LibTomCrypt through 1.18.1 allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local mach...Show more
LibTomCrypt through 1.18.1 allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.Show less
3Arm
DebianTrustedfirmware
3Debian Linux
Mbed TlsMbed Tls
Jun 17, 2026
Apr 10, 2018
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_psk_hint() that could cause a crash on invalid input.
3Arm
DebianTrustedfirmware
3Debian Linux
Mbed TlsMbed Tls
Jun 17, 2026
Apr 10, 2018
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_key_exchange() that could cause a crash on invalid input.
2Arm
Trustedfirmware
2Arm Trusted Firmware
Trusted Firmware A
Jun 5, 2026
Sep 20, 2017
N/A· v4
7.0 HIGH· v3
5.1 MEDIUM· v2
The BL1 FWU SMC handling code in ARM Trusted Firmware before 1.4 might allow attackers to write arbitrary data to secure memory, bypass the bl1_plat_mem_check protection mechanism, cause a denial of service, or possibly...Show more
The BL1 FWU SMC handling code in ARM Trusted Firmware before 1.4 might allow attackers to write arbitrary data to secure memory, bypass the bl1_plat_mem_check protection mechanism, cause a denial of service, or possibly have unspecified other impact via a crafted AArch32 image, which triggers an integer overflow.Show less
2Arm
Trustedfirmware
2Mbed Tls
Mbed Tls
Jun 5, 2026
Aug 30, 2017
N/A· v4
8.1 HIGH· v3
6.8 MEDIUM· v2
ARM mbed TLS before 1.3.21 and 2.x before 2.1.9, if optional authentication is configured, allows remote attackers to bypass peer authentication via an X.509 certificate chain with many intermediates. NOTE: although mbed...Show more
ARM mbed TLS before 1.3.21 and 2.x before 2.1.9, if optional authentication is configured, allows remote attackers to bypass peer authentication via an X.509 certificate chain with many intermediates. NOTE: although mbed TLS was formerly known as PolarSSL, the releases shipped with the PolarSSL name are not affected.Show less
2Arm
Trustedfirmware
2Arm Trusted Firmware
Trusted Firmware A
Jun 8, 2026
Jun 7, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
In ARM Trusted Firmware through 1.3, the secure self-hosted invasive debug interface allows normal world attackers to cause a denial of service (secure world panic) via vectors involving debug exceptions and debug regist...Show more
In ARM Trusted Firmware through 1.3, the secure self-hosted invasive debug interface allows normal world attackers to cause a denial of service (secure world panic) via vectors involving debug exceptions and debug registers.Show less
2Arm
Trustedfirmware
2Arm Trusted Firmware
Trusted Firmware A
Jun 8, 2026
Jun 7, 2017
N/A· v4
8.1 HIGH· v3
6.8 MEDIUM· v2
In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypass the MT_EXECUTE_NEVER protection mechanism. This issue occurs because of inconsistency in the number of execu...Show more
In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypass the MT_EXECUTE_NEVER protection mechanism. This issue occurs because of inconsistency in the number of execute-never bits (one bit versus two bits).Show less