2021-0585 | Google Android MessageQueueBase.h beginRead out-of-bounds write (A-184963385)
|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 8.1/9.0/10.0/11.0 (Smartphone Operating System). It has been classified as critical. Affected is the function
beginWrite/beginRead of the file MessageQueueBase.h. 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 beginWrite and beginRead of MessageQueueBase.h, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-11Android ID: A-184963385
The weakness was published 07/15/2021 as A-184963385. The advisory is available at source.android.com. This vulnerability is traded as CVE-2021-0585 since 11/06/2020. The exploitability is told to be easy. Local access is required to approach this attack. The successful exploitation requires a authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 07/18/2021). 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.
VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.7
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
Class: Memory corruption
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Active Actors: 🔍
Active APT Groups: 🔍Recommended: Patch
0-Day Time: 🔒
11/06/2020 CVE assigned
07/15/2021 +250 days Advisory disclosed
07/15/2021 +0 days VulDB entry created
07/18/2021 +3 days VulDB last updateVendor: https://www.google.com/
CVE: CVE-2021-0585 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
Created: 07/15/2021 11:24
Updated: 07/18/2021 22:45
Changes: (18) vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore
Check our Alexa App!
No comments yet. Please log in to comment.