Google Android fpc_ta_hw_auth.c get_auth_result out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. Impacted is the function get_auth_result of the file fpc_ta_hw_auth.c. Performing a manipulation results in out-of-bounds write.
This vulnerability was named CVE-2020-0011. The attack needs to be approached locally. There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been classified as critical. This affects the function get_auth_result of the file fpc_ta_hw_auth.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In get_auth_result of fpc_ta_hw_auth.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-137648045References: N/A
The weakness was presented 03/10/2020. This vulnerability is uniquely identified as CVE-2020-0011 since 10/17/2019. An attack has to be approached locally. The requirement for exploitation is a authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/11/2020). 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.
See VDB-151237, VDB-151236, VDB-151235 and VDB-151234 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.7
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-bounds writeCWE: CWE-787 / 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 🔍03/10/2020 🔍
03/11/2020 🔍
04/11/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2020-0011 (🔍)
GCVE (CVE): GCVE-0-2020-0011
GCVE (VulDB): GCVE-100-151233
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/11/2020 12:34Updated: 04/11/2024 13:22
Changes: 03/11/2020 12:34 (38), 03/11/2020 12:39 (18), 04/11/2024 13: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.