CVE-2017-14032: High severity Arm mbed TLS vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/mbedtlsto a version that resolves this vulnerability.Fixed in 2.6.0-r0 - Upgrade
Upgrade
alpine/mbedtls2to a version that resolves this vulnerability.Fixed in 2.6.0-r0 - Upgrade
Upgrade
alpine/mbedtls3to a version that resolves this vulnerability.Fixed in 2.6.0-r0 - Upgrade
Upgrade
ARM mbed TLSto a version that resolves this vulnerability.Fixed in 1.3.21 - Upgrade
Upgrade
ARM mbed TLSto a version that resolves this vulnerability.Fixed in 2.1.9
Event History
Frequently Asked Questions
What is the severity of CVE-2017-14032?
CVE-2017-14032 is classified as a medium severity vulnerability.
How do I fix CVE-2017-14032?
To fix CVE-2017-14032, update to mbed TLS version 1.3.21 or 2.1.9 or later.
What types of attacks can CVE-2017-14032 enable?
CVE-2017-14032 can potentially allow remote attackers to bypass peer authentication.
Which versions of mbed TLS are affected by CVE-2017-14032?
CVE-2017-14032 affects mbed TLS versions before 1.3.21 and 2.x before 2.1.9.
Does CVE-2017-14032 impact the security of my application?
Yes, CVE-2017-14032 can compromise the security of applications relying on proper peer authentication.