Raoul Strackx

**Name of the Vulnerable Software and Affected Versions** Arm Mbed TLS versions prior to 2.24.0 **Description** The issue is related to the incorrect use of a revocationDate check when deciding whether to honor certificate revocation via a CRL. This can be exploited by an attacker in certain situations by changing the local clock, potentially affecting data integrity. **Recommendations** For Arm Mbed TLS versions prior to 2.24.0, update to version 2.24.0 or later to resolve the issue. As a temporary workaround, consider restricting access to certificate revocation lists (CRLs) to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Arm Mbed TLS versions prior to 2.23.0 **Description** A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator. This issue is related to the implementation of TLS and SSL protocols in Mbed TLS, allowing an attacker to access confidential data. **Recommendations** For versions prior to 2.23.0, update to version 2.23.0 or later to resolve the issue. As a temporary workaround, consider disabling hardware acceleration for TLS and SSL protocols until a patch is available. Restrict access to sensitive data to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Arm Mbed TLS versions prior to 2.23.0 **Description** The issue is related to a side channel in modular exponentiation, which could disclose an RSA private key used in a secure enclave. This is due to a dependency of the instruction timing on the instruction data, allowing a remote attacker to access confidential data. **Recommendations** For versions prior to 2.23.0, update to version 2.23.0 or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive data handled by the secure enclave until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Arm Mbed TLS versions prior to 2.23.0 **Description** A side channel issue allows the recovery of an ECC private key. This is related to functions such as `mbedtls ecp check pub priv`, `mbedtls pk parse key`, `mbedtls pk parse keyfile`, `mbedtls ecp mul`, and `mbedtls ecp mul restartable`. The issue can be exploited by a remote attacker to gain access to confidential data. **Recommendations** For versions prior to 2.23.0, update to version 2.23.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the functions `mbedtls ecp check pub priv`, `mbedtls pk parse key`, `mbedtls pk parse keyfile`, `mbedtls ecp mul`, and `mbedtls ecp mul restartable` to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Intel SGX (affected versions not specified) Huawei VRP (affected versions not specified) **Description** The issue is related to the implementation of Intel Software Guard Extensions (SGX) technology and speculative execution in microprocessors. It may allow unauthorized disclosure of information from an enclave to an attacker with local user access via a side-channel analysis. This can enable an attacker to read data from the L1 cache, which may contain fragments of data from the protected area after speculative execution. **Recommendations** For Intel SGX, consider disabling speculative execution as a temporary workaround until a patch is available. For Huawei VRP, at the moment, there is no information about a newer version that contains a fix for this vulnerability.