Google Android 11.0/12.0/13.0 NFC SecureNfcEnabler.java isToggleable permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android 11.0/12.0/13.0. Affected is the function isToggleable of the file SecureNfcEnabler.java of the component NFC Handler. This manipulation causes permission.
This vulnerability is registered as CVE-2023-21086. The attack needs to be launched locally. No exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Google Android 11.0/12.0/13.0 (Smartphone Operating System) and classified as critical. Affected by this vulnerability is the function isToggleable of the file SecureNfcEnabler.java of the component NFC Handler. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In isToggleable of SecureNfcEnabler.java and SecureNfcPreferenceController.java, there is a possible way to enable NFC from a secondary account due to a permissions bypass. This could lead to local escalation of privilege from the Guest account with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-238298970
The weakness was published 04/20/2023 as A-238298970. The advisory is shared at source.android.com. This vulnerability is known as CVE-2023-21086 since 11/03/2022. 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/04/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.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2023-0841). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Samsung Exynos
- Samsung Android
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
11/03/2022 🔍04/20/2023 🔍
04/20/2023 🔍
09/04/2025 🔍
Sources
Vendor: google.comAdvisory: A-238298970
Status: Confirmed
CVE: CVE-2023-21086 (🔍)
GCVE (CVE): GCVE-0-2023-21086
GCVE (VulDB): GCVE-100-226885
CERT Bund: WID-SEC-2023-0841 - Samsung Android und Samsung Exynos: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 04/20/2023 07:46Updated: 09/04/2025 01:33
Changes: 04/20/2023 07:46 (44), 05/14/2023 11:41 (11), 09/04/2025 01:33 (22)
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.