dbcve.org
AndroidOperating system · Samsung

CVE-2025-20908

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Use of insufficiently random values in Auracast prior to SMR Mar-2025 Release 1 allows adjacent attackers to access Auracast broadcasting.

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 confidence

Auracast implementations prior to SMR Mar-2025 Release 1 use insufficiently random values in their broadcast functionality. This randomness weakness allows an adjacent attacker within Bluetooth range to predict or derive the values used for broadcast access, enabling unauthorized access to what should be private Auracast broadcasts.

MitigationUpdate Auracast firmware/software to SMR Mar-2025 Release 1 or later to obtain the properly random values. Organizations should inventory Auracast deployments and prioritize updating devices that handle sensitive audio broadcasts.

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
AndroidOperating system
Affected:= 14.0= 15.0

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version
    Go to Settings > About Phone > Android version and confirm it reads 14.0 or 15.0
    Affected if Android version is 14.0 or 15.0 on a Samsung device
  2. Check Samsung Maintenance Release (SMR) version
    Go to Settings > About Phone > Software information > Build number; the SMR version appears in the format SMRx-xxxx (for example, SMR1-xxxx)
    Affected if SMR version is before SMR3-2025 (March 2025 Release 1) or cannot be confirmed as SMR Mar-2025 Release 1 or later
  3. Confirm Auracast functionality is in use
    Check Settings > Connected devices > Auracast or look for Auracast listener/broadcast options in the Bluetooth or quick settings panel
    Affected if Auracast broadcasts are enabled or the device has acted as an Auracast source or listener
  4. Identify Auracast broadcast configuration
    Review Bluetooth sharing settings or any Auracast-specific settings to determine if private or sensitive audio broadcasts are configured
    Affected if Private Auracast broadcasts are active and the device runs the affected Android/SMR combination

A user is affected if their Samsung Android device runs version 14.0 or 15.0 with a Samsung Maintenance Release prior to March 2025 Release 1 AND they have Auracast broadcast functionality enabled or have configured private Auracast broadcasts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Auracast firmware/software to SMR Mar-2025 Release 1 or later to obtain the properly random values. Organizations should inventory Auracast deployments and prioritize updating devices that handle sensitive audio broadcasts.

Recommended fix High confidence

SMR Mar-2025 Release 1 (March 2025 Security Patch Level)

  1. Open Settings on the Samsung device
  2. Navigate to Security and privacy > Security update
  3. Tap on Check for updates to search for the March 2025 security update
  4. Download and install the SMR Mar-2025 Release 1 update if available
  5. Restart the device to complete the installation
  6. Verify the update was applied by checking Settings > Security and privacy > Security update - the security patch level should show March 2025

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20908 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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