Google Android 10.0/11.0/12.0 btm_sec.cc btm_sec_connected/btm_sec_disconnected use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Android 10.0/11.0/12.0. The impacted element is the function btm_sec_connected/btm_sec_disconnected of the file btm_sec.cc. The manipulation leads to use after free.
This vulnerability is uniquely identified as CVE-2021-39674. Local access is required to approach this attack. No exploit exists.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Google Android 10.0/11.0/12.0 (Smartphone Operating System) and classified as critical. This issue affects the function btm_sec_connected/btm_sec_disconnected of the file btm_sec.cc. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 02/12/2022 as A-201083442. It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2021-39674 since 08/23/2021. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/12/2022). It is expected to see the exploit prices for this product increasing in the near future.
Applying a patch is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
08/23/2021 🔍02/12/2022 🔍
02/12/2022 🔍
02/17/2022 🔍
Sources
Vendor: google.comAdvisory: A-201083442
Status: Confirmed
CVE: CVE-2021-39674 (🔍)
GCVE (CVE): GCVE-0-2021-39674
GCVE (VulDB): GCVE-100-192947
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 02/12/2022 10:40Updated: 02/17/2022 07:36
Changes: 02/12/2022 10:40 (42), 02/17/2022 07:36 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.