Local side channel attacks in Mbed TLS


1) Local side channel attack


Risk: Low


CVSSv3.1: 4.8 [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C] [PCI]


CVE-ID: N/A


CWE-ID: CWE-208 - Information Exposure Through Timing Discrepancy


Exploit availability: No


Description

The vulnerability allows a local user to gain access to sensitive information.


The vulnerability exists due to observable timing discrepancy. An attacker with access to precise enough timing and memory access information (for example, able to execute arbitrary code and sharing a memory cache with the victim) can recover the private keys used in static Diffie-Hellman with x25519 and x448.


Mitigation

Install updates from vendor's website.


Vulnerable software versions

mbed TLS: 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9, 1.3.10, 1.3.11, 1.3.12, 1.3.13, 1.3.14, 1.3.15, 1.3.16, 1.3.17, 1.3.18, 1.3.19, 1.3.20, 1.3.21, 1.3.22, 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12, 2.1.13, 2.1.14, 2.1.15, 2.1.16, 2.1.17, 2.1.18, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.14, 2.7.15, 2.7.16, 2.7.17, 2.7.18, 2.7.19, 2.8.0, 2.9.0, 2.10.0, 2.11.0, 2.12.0, 2.13.0, 2.13.1, 2.14.0, 2.14.1, 2.15.0, 2.15.1, 2.16.0, 2.16.1, 2.16.2, 2.16.3, 2.16.4, 2.16.5, 2.16.6, 2.16.7, 2.16.8, 2.16.9, 2.16.10, 2.17.0, 2.18.0, 2.18.1, 2.19.0, 2.19.1, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.24.0, 2.25.0, 2.26.0


mbed Crypto: 0.1.0a, 0.1.0b, 0.1.0b2, 1.0.0, 1.0.0d0, 1.0.0d1, 1.0.0d2, 1.0.0d3, 1.0.0d4, 1.0.0d5, 1.0.0d6, 1.0.0d7, 1.1.0, 1.1.0d0, 1.1.0d1, 1.1.0d2, 1.1.1, 2.0.0, 2.0.0d0, 2.0.0d1, 2.0.0d2, 2.1.0d0, 3.0.0, 3.0.0d0, 3.0.1, 3.1.0


CPE
External links

https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2021-07-2


Q & A


Can this vulnerability be exploited remotely?


No. This vulnerability can be exploited locally. The attacker should have authentication credentials and successfully authenticate on the system.


Is there known malware, which exploits this vulnerability?


No. We are not aware of malware exploiting this vulnerability.



2) local channel attacks