CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Google Android 11.0. Affected is an unknown function of the component Settings Handler. The manipulation leads to permissions. This vulnerability is traded as CVE-2020-0331. Attacking locally is a requirement. There is no exploit available. It is recommended to apply a patch to fix this issue. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 11.0 (Smartphone Operating System). This issue affects some unknown functionality of the component Settings Handler. The manipulation with an unknown input leads to a permissions vulnerability. Using CWE to declare the problem leads to CWE-281. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. Impacted is confidentiality. The summary by CVE is:
In Settings, there is a possible permissions bypass. This could lead to local information disclosure of the device's IMEI with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-147309310
The weakness was disclosed 09/18/2020 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2020-0331 since 10/17/2019. An attack has to be approached locally. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Applying a patch is able to eliminate this problem.
The entries VDB-161398, VDB-161399, VDB-161402 and VDB-161403 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: PermissionsCWE: CWE-281 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
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
10/17/2019 🔍09/18/2020 🔍
09/19/2020 🔍
09/19/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2020-0331 (🔍)
GCVE (CVE): GCVE-0-2020-0331
GCVE (VulDB): GCVE-100-161597
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/19/2020 08:43Updated: 09/19/2020 08:48
Changes: 09/19/2020 08:43 (40), 09/19/2020 08:48 (18)
Complete: 🔍
Cache ID: 216:459:103
No comments yet. Languages: en.
Please log in to comment.