CVE-2025-0079
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 multiple locations, there is a possible way that avdtp and avctp channels could be unencrypted due to a logic error in the code. This could lead to local escalation of privilege with User 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 confidenceThis is a local privilege escalation vulnerability in Android's Bluetooth stack. A logic error in multiple locations causes avdtp (Audio/Video Distribution Transport Protocol) and avctp (Audio/Video Control Transport Protocol) channels to transmit unencrypted when encryption should be applied, allowing a local attacker to potentially intercept or manipulate Bluetooth A/V communications.
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.0= 12.1= 13.0= 14.0= 15.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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Check Android OS versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADBAffected if The version is 12.0, 12.1, 13.0, 14.0, or 15.0
-
Verify Bluetooth is enabledCheck Settings > Bluetooth or run 'settings get global bluetooth_on' via ADBAffected if Bluetooth is turned on (the vulnerability requires Bluetooth to be active)
-
Identify if A/V Bluetooth profiles are in useCheck for paired devices using A2DP, AVCRP, or other audio profiles via 'dumpsys bluetooth_manager' or in Settings > Bluetooth > Paired devicesAffected if Bluetooth A/V profiles (A2DP, AVCTP, AVDTP) are actively used or paired with devices
If the Android version is 12.0, 12.1, 13.0, 14.0, or 15.0 and Bluetooth A/V communications are in use, the environment is likely affected by this encryption bypass vulnerability.
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 patch for CVE-2025-0079 which corrects the logic error in the avdtp/avctp encryption handling code. Verify that Bluetooth A/V connections are properly encrypted after the update.
Android 14: Update to February 2025 security patch level or later; Android 13: Update to February 2025 security patch level or later; Android 12.0/12.1: Update to February 2025 security patch level or later
- Check your device's current Android version in Settings > About Phone > Android version
- Check your device's current security patch level in Settings > About Phone > Security patch level
- Apply the latest Android security update for your device. For Android 14, 13, 12.0, and 12.1, install the February 2025 security patch or later
- Verify the security patch level has been updated after installation
- If your device manufacturer has not released an update, consider checking for available system webview updates and apply them
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0079 — 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-2025-0079 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