CVE-2021-1017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn AdapterService and GattService definition of AndroidManifest.xml, there is a possible way to disable bluetooth connection due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-12Android ID: A-182583850
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis vulnerability in Android-12's AdapterService and GattService components lacks proper permission checks in their AndroidManifest.xml definitions. This missing permission check allows a local attacker to potentially disable Bluetooth connections, achieving local privilege escalation without requiring additional execution privileges. User interaction is required for successful exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Android version is 12.0Check Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device runs Android 12.0 (not 12.1, 12.2, or later) where the vulnerable permission checks are missing
-
Verify Bluetooth is enabledCheck Settings > Bluetooth is turned ON, or run 'settings get global bluetooth_on' via ADB shell returns '1'Affected if Bluetooth is enabled and the vulnerable AdapterService/GattService components are active
-
Inspect AndroidManifest.xml for AdapterService permission gapLocate the Bluetooth APK (typically /system/priv-app/Bluetooth*.apk), decompile, and check AndroidManifest.xml for <service android:name='.AdapterService'> without android:permission attributeAffected if The AdapterService definition lacks a android:permission attribute, allowing any local app to bind to it
-
Inspect AndroidManifest.xml for GattService permission gapSame as above, check for <service android:name='.GattService'> without android:permission attribute in the Bluetooth app manifestAffected if The GattService definition lacks a android:permission attribute, allowing any local app to bind to it
A device is affected if it runs Android 12.0 with Bluetooth enabled and the Bluetooth app's AndroidManifest.xml shows AdapterService and/or GattService without android:permission attributes defined.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the Google security patch for Android-12 (Android ID A-182583850) which adds proper permission validation to the vulnerable Bluetooth services in AndroidManifest.xml. Users should update to the latest Android security update.
Android 13 or later, or Android 12 with latest security patch level
- 1. Navigate to Settings > System > System Update on the Android device
- 2. Check for and install any available Android security updates
- 3. If Android 12 security updates are not available or the issue persists, upgrade to Android 13 or later by going to Settings > System > System Update > Check for Update
- 4. Alternatively, ensure the device receives the monthly Android security patch level that includes the fix for CVE-2021-1017 (Android ID: A-182583850)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-1017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data