Google Android Shared Memory ashmem.c calc_vm_may_flags default permission

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 classified as critical was found in Google Android (Smartphone Operating System) (affected version not known). This vulnerability affects the function calc_vm_may_flags of the file ashmem.c of the component Shared Memory. The manipulation with an unknown input leads to a default permission vulnerability. The CWE definition for the vulnerability is CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In calc_vm_may_flags of ashmem.c, there is a possible arbitrary write to shared memory due to a permissions bypass. This could lead to local escalation of privilege by corrupting memory shared between processes, with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-142938932

The weakness was disclosed 01/08/2020 (Website). The advisory is available at This vulnerability was named CVE-2020-0009 since 10/17/2019. Local access is required to approach this attack. A single authentication is required for exploitation. Technical details and also a public exploit are known. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/06/2024). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1222 by the MITRE ATT&CK project.

It is possible to download the exploit at It is declared as proof-of-concept. As 0-day the estimated underground price was around $25k-$100k.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at Exploit-DB (47921). The entries VDB-37279, VDB-39449, VDB-40633 and VDB-57226 are pretty similar.






CPE 2.3info

CPE 2.2info


VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍


VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍



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

NVD Base Score: 🔍


Class: Default permission
CWE: CWE-276 / CWE-266

Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Exploit-DB: 🔍

Threat Intelligenceinfo

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


Recommended: Patch
Status: 🔍

0-Day Time: 🔍


10/17/2019 🔍
01/08/2020 +83 days 🔍
01/08/2020 +0 days 🔍
06/06/2024 +1611 days 🔍



Advisory: 155903
Status: Not defined

CVE: CVE-2020-0009 (🔍)
scip Labs:
See also: 🔍


Created: 01/08/2020 07:08 PM
Updated: 06/06/2024 04:34 AM
Changes: 01/08/2020 07:08 PM (40), 01/08/2020 07:13 PM (18), 03/20/2024 08:32 AM (18), 03/20/2024 08:35 AM (1), 06/06/2024 04:34 AM (11)
Complete: 🔍
Cache ID: 44:ACC:40


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!