Security readout for executives and security teams
Plain-English summary
CVE-2023-21247 is an Android Settings flaw that can let a local actor bypass a device policy restriction related to Bluetooth scanning controls. It matters most for managed Android fleets where policy enforcement is part of security posture.
Executive priority
Treat as a managed-device policy enforcement risk. It is not documented as remotely exploitable or actively exploited, but unpatched Android 12 through 13 devices may undermine administrative controls.
Technical view
The issue is in getAvailabilityStatus of BluetoothScanningMainSwitchPreferenceController.java. A missing permission check may allow bypass of a device policy restriction, causing local escalation of privilege without additional execution privileges or user interaction.
Likely exposure
The source bundle lists Google Android 12, 12L, and 13 as affected. Exposure is most relevant to devices running those versions without the July 2023 Android security update or downstream vendor equivalent.
Exploitation context
The provided sources state local privilege escalation and no required user interaction. They do not show public exploitation, and KEV status is false in the bundle.
Researcher notes
No CVSS, CWE, or detailed exploit conditions are provided in the bundle. Analysis should stay anchored to the missing permission check, affected Android versions, and the Android Settings commit referenced by Google.
Mitigation direction
- Apply Android security updates from July 2023 or later where available.
- Verify OEM firmware includes the referenced Android Settings fix.
- Prioritize managed or enterprise Android devices with Bluetooth scanning policy controls.
- Check Google and device-vendor advisories for model-specific update availability.
Validation and detection
- Inventory Android devices by OS version and security patch level.
- Confirm affected devices are not on Android 12, 12L, or 13 without the fix.
- Review MDM compliance reports for July 2023 or later patch levels.
- Check vendor build notes against the referenced Android bulletin and commit.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2023-21247 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.