TLS hostname validation issues within AWS IoT Device SDKs on Windows
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.3.3, 1.5.18, 1.12.7, 1.5.3, 1.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Connections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.3.3), Python (versions prior to 1.5.18), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.1) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on Windows. This issue has been addressed in aws-c-io submodule versions 0.9.13 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.3.3 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.5.18 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Microsoft Windows. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Microsoft Windows.
Timeline
- CVE published
- Record last updated
Affected versions
- Amazon Web Services AWS IoT Device SDK v2 for Java
fixed in 1.3.3
- Amazon Web Services AWS IoT Device SDK v2 for Python
fixed in 1.5.18
- Amazon Web Services AWS IoT Device SDK v2 for C++
fixed in 1.12.7
- Amazon Web Services AWS IoT Device SDK v2 for Node.js
fixed in 1.5.3
- Amazon Web Services AWS-C-IO
0.9.12
- software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdkMaven
fixed in 1.3.3
- aws-iot-device-sdk-v2npm
fixed in 1.5.1
- awsiotsdkPyPI
fixed in 1.5.18