Google Android binder.c binder_free_transaction use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android. Affected by this issue is the function binder_free_transaction of the file binder.c. This manipulation causes use after free.
This vulnerability is handled as CVE-2019-2213. It is possible to launch the attack on the local host. There is not any exploit available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (affected version unknown). Affected by this vulnerability is the function binder_free_transaction of the file binder.c. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In binder_free_transaction of binder.c, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-133758011References: Upstream kernel
The weakness was released 11/13/2019. This vulnerability is known as CVE-2019-2213 since 12/10/2018. Attacking locally is a requirement. The successful exploitation needs a single authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/13/2024). 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.
Entries connected to this vulnerability are available at VDB-145533, VDB-145532, VDB-145530 and VDB-145529. Statistical analysis made it clear that VulDB provides the best quality for 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: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Use after freeCWE: CWE-416 / 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
12/10/2018 🔍11/13/2019 🔍
11/15/2019 🔍
02/13/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2019-2213 (🔍)
GCVE (CVE): GCVE-0-2019-2213
GCVE (VulDB): GCVE-100-145531
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/15/2019 06:42Updated: 02/13/2024 18:18
Changes: 11/15/2019 06:42 (39), 11/15/2019 06:47 (18), 02/13/2024 18:18 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.