Google Android 10.0 nfa_dm_ndef.c nfa_dm_ndef_find_next_handler out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Android 10.0. This impacts the function nfa_dm_ndef_find_next_handler of the file nfa_dm_ndef.c. Performing a manipulation results in out-of-bounds.
This vulnerability is identified as CVE-2020-0143. The attack is only possible with local access. There is not any exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android 10.0 (Smartphone Operating System). It has been classified as problematic. This affects the function nfa_dm_ndef_find_next_handler of the file nfa_dm_ndef.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:
In nfa_dm_ndef_find_next_handler of nfa_dm_ndef.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure of heap data via compromised device firmware with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-145597277
The weakness was released 06/11/2020. This vulnerability is uniquely identified as CVE-2020-0143 since 10/17/2019. An attack has to be approached locally. Required for exploitation is a authentication. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-156565, VDB-156564, VDB-156563 and VDB-156562. 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: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.4
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: Out-of-boundsCWE: CWE-125 / CWE-119
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 🔍06/11/2020 🔍
06/12/2020 🔍
06/12/2020 🔍
Sources
Vendor: google.comStatus: Not defined
CVE: CVE-2020-0143 (🔍)
GCVE (CVE): GCVE-0-2020-0143
GCVE (VulDB): GCVE-100-156561
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/12/2020 08:17Updated: 06/12/2020 08:22
Changes: 06/12/2020 08:17 (39), 06/12/2020 08:22 (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.