| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android and classified as critical. The impacted element is the function binder_thread_read of the file binder.c. The manipulation results in use after free.
This vulnerability is known as CVE-2019-2025. Attacking locally is a requirement. Furthermore, an exploit is available.
A patch should be applied to remediate this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (the affected version is unknown). It has been classified as critical. Affected is the function binder_thread_read of the file binder.c. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In binder_thread_read of binder.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-116855682References: Upstream kernel
The bug was discovered 11/23/2018. The weakness was published 06/19/2019. This vulnerability is traded as CVE-2019-2025 since 12/10/2018. Local access is required to approach this attack. A authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 208 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at Exploit-DB (46503). Similar entries are available at VDB-136769, VDB-136768, VDB-136767 and VDB-136766. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
11/23/2018 🔍12/10/2018 🔍
06/19/2019 🔍
06/20/2019 🔍
06/06/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2019-2025 (🔍)
GCVE (CVE): GCVE-0-2019-2025
GCVE (VulDB): GCVE-100-136770
OSVDB: - Google Android binder privilege escalation
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/20/2019 13:40Updated: 06/06/2024 06:00
Changes: 06/20/2019 13:40 (41), 06/26/2020 11:28 (18), 10/07/2023 09:43 (4), 06/06/2024 06:00 (22)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.