Information disclosure in mbed TLS
| Risk | Low |
| Patch available | YES |
| Number of vulnerabilities | 1 |
| CVE-ID | CVE-2013-0169 |
| CWE-ID | CWE-310 |
| Exploitation vector | Network |
| Public exploit | Public exploit code for vulnerability #1 is available. |
| Vulnerable software |
mbed TLS Universal components / Libraries / Libraries used by multiple products |
| Vendor | ARM |
Security Bulletin
This security bulletin contains one low risk vulnerability.
1) Cryptographic issues
EUVDB-ID: #VU33317
Risk: Low
CVSSv4.0: 2.9 [CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/U:Clear]
CVE-ID: CVE-2013-0169
CWE-ID:
CWE-310 - Cryptographic Issues
Exploit availability: Yes
DescriptionThe vulnerability allows a remote non-authenticated attacker to gain access to sensitive information.
The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue. Per http://www.openssl.org/news/vulnerabilities.html: Fixed in OpenSSL 1.0.1d (Affected 1.0.1c, 1.0.1b, 1.0.1a, 1.0.1) Fixed in OpenSSL 1.0.0k (Affected 1.0.0j, 1.0.0i, 1.0.0g, 1.0.0f, 1.0.0e, 1.0.0d, 1.0.0c, 1.0.0b, 1.0.0a, 1.0.0) Fixed in OpenSSL 0.9.8y (Affected 0.9.8x, 0.9.8w, 0.9.8v, 0.9.8u, 0.9.8t, 0.9.8s, 0.9.8r, 0.9.8q, 0.9.8p, 0.9.8o, 0.9.8n, 0.9.8m, 0.9.8l, 0.9.8k, 0.9.8j, 0.9.8i, 0.9.8h, 0.9.8g, 0.9.8f, 0.9.8d, 0.9.8c, 0.9.8b, 0.9.8a, 0.9.8) Affected users should upgrade to OpenSSL 1.0.1e, 1.0.0k or 0.9.8y (The fix in 1.0.1d wasn't complete, so please use 1.0.1e or later)
MitigationInstall update from vendor's website.
Vulnerable software versionsmbed TLS: 1.1.0 - 1.2.5
CPE2.3- cpe:2.3:a:arm:mbed_tls:1.1.0:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.1.1:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.1.2:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.1.3:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.1.4:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.1.5:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.2.0:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.2.1:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.2.2:*:*:*:*:*:*:*
- cpe:2.3:a:arm:mbed_tls:1.2.3:*:*:*:*:*:*:*
Q & A
Can this vulnerability be exploited remotely?
Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the Internet.
Is there known malware, which exploits this vulnerability?
No. We are not aware of malware exploiting this vulnerability. However, proof of concept for this vulnerability is available.
