Google Android 8.0/8.1/9.0/10.0 Sensor.cpp flattenString8 uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google Android 8.0/8.1/9.0/10.0. Affected by this issue is the function flattenString8 of the file Sensor.cpp. The manipulation leads to use of uninitialized resource.
This vulnerability is uniquely identified as CVE-2020-0007. Local access is required to approach this attack. No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 8.0/8.1/9.0/10.0 (Smartphone Operating System). This issue affects the function flattenString8 of the file Sensor.cpp. The manipulation with an unknown input leads to a use of uninitialized resource vulnerability. Using CWE to declare the problem leads to CWE-1187. This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908. Impacted is confidentiality. The summary by CVE is:
In flattenString8 of Sensor.cpp, there is a possible information disclosure of heap memory due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android-8.0, Android-8.1, Android-9, and Android-10 Android ID: A-141890807
The weakness was disclosed 01/08/2020 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2020-0007 since 10/17/2019. An attack has to be approached locally. The successful exploitation needs a simple authentication. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem.
The entries VDB-148458, VDB-148456, VDB-148455 and VDB-148454 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best 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: 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: Use of uninitialized resourceCWE: CWE-1187 / CWE-908
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
10/17/2019 🔍01/08/2020 🔍
01/09/2020 🔍
01/09/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2020-0007 (🔍)
GCVE (CVE): GCVE-0-2020-0007
GCVE (VulDB): GCVE-100-148457
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/09/2020 10:10Updated: 01/09/2020 10:15
Changes: 01/09/2020 10:10 (41), 01/09/2020 10:15 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.