CVE-2021-40831: Missing SNI validation and inconsistent CA override function behavior within AWS IoT Device SDKs on Apple devices

Published Nov 22, 2021
·
Updated

The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been "overridden". TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The awstlsctxoptionsoverridedefaulttruststore function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS.

Other sources

The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been “overridden”. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'awstlsctxoptionsoverridedefaulttruststore' function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS.

Affected Software

15 affected componentsFixes available
pip/awsiotsdk<1.7.0
1.7.0
npm/aws-iot-device-sdk-v2<1.6.0
1.6.0
maven/software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk<1.5.0
1.5.0
All of the following
Any of the following
Amazon Amazon Web Services AWS-C-IO=0.10.7
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Java<1.5.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Node.js<1.6.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Python<1.7.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 C\+\+<1.14.0
Apple macOS
Amazon Amazon Web Services AWS-C-IO=0.10.7
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Java<1.5.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Node.js<1.6.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 Python<1.7.0
Amazon Amazon Web Services Internet Of Things Device Software Development Kit V2 C\+\+<1.14.0
Apple macOS

Remediation

Information

Update to the latest versions of the AWS IoT Device SDK.

Event History

Nov 22, 2021
CVE Published
via MITRE·11:41 PM
Data Sourced
via MITRE·11:41 PM
RemedyDescriptionSeverityWeakness
Nov 24, 2021
Advisory Published
via GitHub·08:35 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2021-40831?

The severity of CVE-2021-40831 is high with a score of 7.2.

2

Which software versions are affected by CVE-2021-40831?

The affected software versions are Amazon AWS-C-IO 0.10.7, Amazon IoT Device SDK v2 for Java up to version 1.5.0, Node.js up to version 1.6.0, Python up to version 1.7.0, and C++ up to version 1.14.0.

3

What does CVE-2021-40831 impact on macOS systems?

On macOS systems, CVE-2021-40831 impacts the AWS IoT Device SDK v2 for Java, Python, C++, and Node.js by appending a user supplied Certificate Authority (CA) to the root CAs instead of overriding it, and by not enabling SNI validation when the CA has been "overridden".

4

How can I fix CVE-2021-40831?

To fix CVE-2021-40831, update the affected software versions to the latest available versions provided by Amazon.

5

Is Apple macOS vulnerable to CVE-2021-40831?

No, Apple macOS is not vulnerable to CVE-2021-40831.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203