Google Android 11.0 Foreground ActiveServices.java bindServiceLocked Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 11.0. It has been rated as problematic. The impacted element is the function bindServiceLocked of the file ActiveServices.java of the component Foreground Handler. The manipulation leads to an unknown weakness.
This vulnerability is documented as CVE-2021-0398. The attack needs to be performed locally. There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 11.0 (Smartphone Operating System). This issue affects the function bindServiceLocked of the file ActiveServices.java of the component Foreground Handler. Impacted is confidentiality, integrity, and availability.
The weakness was released 03/11/2021 as A-173516292. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2021-0398. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 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: Local Privilege EscalationCWE: Unknown
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/06/2020 🔍03/11/2021 🔍
03/11/2021 🔍
03/31/2021 🔍
Sources
Vendor: google.comAdvisory: A-173516292
Status: Confirmed
CVE: CVE-2021-0398 (🔍)
GCVE (CVE): GCVE-0-2021-0398
GCVE (VulDB): GCVE-100-171101
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/11/2021 11:51Updated: 03/31/2021 11:01
Changes: 03/11/2021 11:51 (40), 03/31/2021 10:56 (5), 03/31/2021 11:01 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.