cve.bz

CVE-2021-40830 amazon: Improper Certificate Validation

8.8 highEPSS 0.4%Fix available

High (8.8) in amazon. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk 1.5.0.

On this page
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 Unix systems. 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 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust store. This corrects this issue. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Linux/Unix. Amazon Web Services AWS-C-IO 0.10.4 on Linux/Unix.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk (Maven): fixed in 1.5.0
  • aws-iot-device-sdk-v2 (npm): fixed in 1.5.3
  • awsiotsdk (PyPI): fixed in 1.6.1

Ask an AI about this CVE

Show the promptExplain CVE-2021-40830 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-40830?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-40830?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-40830 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Amazon Web Services AWS IoT Device SDK v2 for Javabefore 1.5.0
Amazon Web Services AWS IoT Device SDK v2 for Pythonbefore 1.6.1
Amazon Web Services AWS IoT Device SDK v2 for C++before 1.12.7
Amazon Web Services AWS IoT Device SDK v2 for Node.jsbefore 1.5.3
Amazon Web Services AWS-C-IO0.10.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c4rh-4376-gff4Mavensoftware.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk<1.5.01.5.0
GHSA-c4rh-4376-gff4npmaws-iot-device-sdk-v2<1.5.31.5.3
GHSA-c4rh-4376-gff4PyPIawsiotsdk<1.6.11.6.1
PYSEC-2021-863PyPIawsiotsdk<1.6.11.6.1

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON