Google Android 11.0/12.0 ActiveServices.java shouldAllowFgsWhileInUsePermissionLocked permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 11.0/12.0. It has been rated as critical. The affected element is the function shouldAllowFgsWhileInUsePermissionLocked of the file ActiveServices.java. Performing a manipulation results in permission.
This vulnerability is reported as CVE-2022-20356. The attack requires a local approach. No exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in Google Android 11.0/12.0 (Smartphone Operating System). This affects the function shouldAllowFgsWhileInUsePermissionLocked of the file ActiveServices.java. The manipulation with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In shouldAllowFgsWhileInUsePermissionLocked of ActiveServices.java, there is a possible way to start foreground service from background due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12LAndroid ID: A-215003903
The weakness was disclosed 08/11/2022 as A-215003903. The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2022-20356 since 10/14/2021. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/08/2025). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1222 for this issue.
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: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
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/14/2021 🔍08/11/2022 🔍
08/11/2022 🔍
09/08/2025 🔍
Sources
Vendor: google.comAdvisory: A-215003903
Status: Confirmed
CVE: CVE-2022-20356 (🔍)
GCVE (CVE): GCVE-0-2022-20356
GCVE (VulDB): GCVE-100-206157
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 08/11/2022 10:39Updated: 09/08/2025 22:24
Changes: 08/11/2022 10:39 (43), 09/10/2022 08:43 (11), 09/08/2025 22:24 (15)
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.