CVE-2017-14032

Name: CVE-2017-14032
Creator: NVD / NIST
Published: 2017-08-30T20:29:00.337+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.49%

Last modified Jun 17, 2026

CVE-2017-14032 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.49% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability

1.49%

70.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-287

Affected Software

Vendor	Product	Versions
Arm	Mbed Tls	1.3.19
Arm	Mbed Tls	1.3.21
Arm	Mbed Tls	2.1.7
Arm	Mbed Tls	2.1.9
Arm	Mbed Tls	2.4.2
Arm	Mbed Tls	2.6.2
Trustedfirmware	Mbed Tls	1.3.10
Trustedfirmware	Mbed Tls	1.3.11
Trustedfirmware	Mbed Tls	1.3.12
Trustedfirmware	Mbed Tls	1.3.13
Trustedfirmware	Mbed Tls	1.3.14
Trustedfirmware	Mbed Tls	1.3.15
Trustedfirmware	Mbed Tls	1.3.16
Trustedfirmware	Mbed Tls	1.3.17
Trustedfirmware	Mbed Tls	1.3.18
Trustedfirmware	Mbed Tls	1.3.20
Trustedfirmware	Mbed Tls	2.0.0
Trustedfirmware	Mbed Tls	2.1.0
Trustedfirmware	Mbed Tls	2.1.1
Trustedfirmware	Mbed Tls	2.1.2
Trustedfirmware	Mbed Tls	2.1.3
Trustedfirmware	Mbed Tls	2.1.4
Trustedfirmware	Mbed Tls	2.1.5
Trustedfirmware	Mbed Tls	2.1.6
Trustedfirmware	Mbed Tls	2.1.8
Trustedfirmware	Mbed Tls	2.2.0
Trustedfirmware	Mbed Tls	2.2.1
Trustedfirmware	Mbed Tls	2.3.0
Trustedfirmware	Mbed Tls	2.4.0
Trustedfirmware	Mbed Tls	2.5.1

References

http://www.debian.org/security/2017/dsa-3967
https://bugs.debian.org/873557Issue Tracking, Patch, Third Party Advisory
https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32Issue Tracking, Patch, Third Party Advisory
https://github.com/ARMmbed/mbedtls/commit/d15795acd5074e0b44e71f7ede8bdfe1b48591fcIssue Tracking, Patch, Third Party Advisory
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02Vendor Advisory
http://www.debian.org/security/2017/dsa-3967
https://bugs.debian.org/873557Issue Tracking, Patch, Third Party Advisory
https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32Issue Tracking, Patch, Third Party Advisory
https://github.com/ARMmbed/mbedtls/commit/d15795acd5074e0b44e71f7ede8bdfe1b48591fcIssue Tracking, Patch, Third Party Advisory
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02Vendor Advisory

Timeline

Published: Aug 30, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-14032?

How severe is CVE-2017-14032?

Severity scoring for CVE-2017-14032 is pending analysis. The EPSS model estimates a 1.49% probability of exploitation in the next 30 days.

How do I fix CVE-2017-14032?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-14032?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST