Google Android 10.0/11.0/12.0 SecureNfcPreferenceController.java setChecked 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 10.0/11.0/12.0. It has been classified as critical. Affected is the function setChecked
of the file SecureNfcPreferenceController.java. The manipulation leads to permission.
This vulnerability is traded as CVE-2022-20360. The attack needs to be approached locally. There is no exploit available.
It is recommended to apply a patch to fix this issue.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Google Android 10.0/11.0/12.0 (Smartphone Operating System) and classified as critical. This issue affects the function setChecked
of the file SecureNfcPreferenceController.java. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In setChecked of SecureNfcPreferenceController.java, there is a missing permission check. This could lead to local escalation of privilege from the guest user with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-228314987
The weakness was shared 08/11/2022 as A-228314987. It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2022-20360 since 10/14/2021. 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 09/10/2022). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
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
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: 🔍
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/10/2022 🔍
Sources
Vendor: google.comAdvisory: A-228314987
Status: Confirmed
CVE: CVE-2022-20360 (🔍)
GCVE (CVE): GCVE-0-2022-20360
GCVE (VulDB): GCVE-100-206159
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 08/11/2022 10:40Updated: 09/10/2022 08:45
Changes: 08/11/2022 10:40 (43), 09/10/2022 08:45 (11)
Complete: 🔍
Cache ID: 216:367:103
No comments yet. Languages: en.
Please log in to comment.