| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been rated as critical. This affects an unknown function of the component seccomp Policy Handler. Performing a manipulation results in access control. This vulnerability is known as CVE-2019-2054. Attacking locally is a requirement. No exploit is available. It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical has been found in Google Android (Smartphone Operating System) (version unknown). This affects an unknown function of the component seccomp Policy Handler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the seccomp implementation prior to kernel version 4.8, there is a possible seccomp bypass due to seccomp policies that allow the use of ptrace. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-119769499
The bug was discovered 11/19/2018. The weakness was published 05/08/2019 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2019-2054 since 12/10/2018. An attack has to be approached locally. The successful exploitation requires a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 170 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
Similar entries are available at VDB-134453, VDB-134495, VDB-134496 and VDB-134497. 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: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Access controlCWE: CWE-264
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
11/19/2018 🔍12/10/2018 🔍
05/08/2019 🔍
05/09/2019 🔍
09/15/2023 🔍
Sources
Vendor: google.comAdvisory: 153799
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-2054 (🔍)
GCVE (CVE): GCVE-0-2019-2054
GCVE (VulDB): GCVE-100-134505
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/09/2019 12:46Updated: 09/15/2023 09:06
Changes: 05/09/2019 12:46 (58), 09/11/2020 10:38 (2), 09/15/2023 09:03 (4), 09/15/2023 09:06 (1)
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.