AWS IoT Device SDK v2 aws-c-io Submodule and/or certificate validation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in AWS IoT Device SDK v2. This issue affects the function aws_tls_ctx_options_override_default_trust_store_* of the file and/or of the component aws-c-io Submodule. Performing a manipulation results in certificate validation. This vulnerability is known as CVE-2021-40830. Access to the local network is required for this attack. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in AWS IoT Device SDK v2 (affected version unknown). It has been classified as problematic. This affects the function aws_tls_ctx_options_override_default_trust_store_* of the file and/or of the component aws-c-io Submodule. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was published 11/23/2021. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-40830 since 09/09/2021. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.

Upgrading eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 5.0

VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.3
CNA Vector (F-Secure): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Certificate validation
CWE: CWE-295 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/09/2021 🔍
11/23/2021 +75 days 🔍
11/23/2021 +0 days 🔍
11/25/2021 +2 days 🔍

Sourcesinfo

Advisory: github.com
Status: Confirmed

CVE: CVE-2021-40830 (🔍)
GCVE (CVE): GCVE-0-2021-40830
GCVE (VulDB): GCVE-100-187125

Entryinfo

Created: 11/23/2021 07:49
Updated: 11/25/2021 19:33
Changes: 11/23/2021 07:49 (49), 11/25/2021 19:27 (1), 11/25/2021 19:33 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!