CVE-2024-0028
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 Audio Service, there is a possible way to obtain MAC addresses of nearby Bluetooth devices due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 · moderate confidenceIn Android's Audio Service, a missing permission check allows a local attacker to obtain MAC addresses of nearby Bluetooth devices without any special privileges or user interaction, leading to local privilege escalation.
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= 16.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Android version is 16.0Check Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shellAffected if Android version equals 16.0 exactly (the only affected version)
-
Confirm Audio Service is accessibleCheck if com.android.server.audio.AudioService or android.media.AudioManager is available on the deviceAffected if Audio Service is present and operational on Android 16.0
-
Verify Bluetooth is enabledCheck Settings > Bluetooth is ON, or run 'settings get global bluetooth_on' in ADB shellAffected if Bluetooth is enabled - the vulnerability allows enumeration of nearby Bluetooth device MAC addresses
-
Confirm Audio Service can access Bluetooth hardwareAttempt to query Bluetooth adapter through Audio Service context, or verify BluetoothAdapter.getDefaultAdapter() returns a valid adapterAffected if Audio Service can access Bluetooth without proper permission checks
The environment is affected if running Android 16.0 with Bluetooth enabled and the Audio Service can access Bluetooth device enumeration without proper permission checks.
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 vendor-supplied security patch for CVE-2024-0028 which adds proper permission verification to the Audio Service before allowing Bluetooth device enumeration.
- Check the Android Security Bulletin for the month the CVE-2024-0028 patch was released to identify the specific security patch level containing the fix
- Apply the latest Android security update available for your Android 16.0 device
- Verify the security patch level by going to Settings > About Phone > Security Patch Level and confirming it includes the fix for CVE-2024-0028
- If no update is available from your device manufacturer, contact the device vendor for timeline on patch delivery
- For enterprise environments, ensure Mobile Device Management (MDM) policies enforce the latest security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0028 — 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-2024-0028 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