TLS hostname validation issues within AWS IoT Device SDKs on Windows
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Amazon Web Services | AWS IoT Device SDK v2 for Java | affected |
|
||||||
| Amazon Web Services | AWS IoT Device SDK v2 for Python | affected |
|
||||||
| Amazon Web Services | AWS IoT Device SDK v2 for C++ | affected |
|
||||||
| Amazon Web Services | AWS IoT Device SDK v2 for Node.js | affected |
|
||||||
| Amazon Web Services | AWS-C-IO | affected |
|
Configuration 1 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
Update to the latest versions of the AWS IoT Device SDK.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0028 | 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. |
Github GHSA |
GHSA-94jq-q5v2-76wj | Improper certificate management in AWS IoT Device SDK v2 |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.411% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.