Google Android memory_group_manager.c mgm_alloc_page out-of-bounds write
|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.
A vulnerability was found in Google Android (Smartphone Operating System) (version unknown). It has been classified as critical. Affected is the function
mgm_alloc_page of the file memory_group_manager.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-787. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In mgm_alloc_page of memory_group_manager.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-201677538References: N/A
The weakness was released 01/15/2022 as A-201677538. The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2021-39682 since 08/23/2021. The exploitability is told to be easy. The attack needs to be approached locally. A authentication is necessary for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/19/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.
CVSSv3VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Memory corruption
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline08/23/2021 CVE assigned
01/15/2022 +145 days Advisory disclosed
01/15/2022 +0 days VulDB entry created
01/19/2022 +4 days VulDB last update
CVE: CVE-2021-39682 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
EntryCreated: 01/15/2022 07:47 AM
Updated: 01/19/2022 11:27 AM
Changes: (1) source_cve_nvd_summary
Do you want to use VulDB in your project?
Use the official API to access entries easily!