CVE-2021-25453
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 · uneditedSome improper access control in Bluetooth APIs prior to SMR Sep-2021 Release 1 allows untrusted application to get Bluetooth information.
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 confidenceImproper access control in Samsung's Bluetooth APIs allows untrusted applications to access Bluetooth information without proper permission validation. This enables any installed app to retrieve sensitive Bluetooth details (such as device names, addresses, or paired device information) that should require elevated privileges.
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= 8.1= 9.0= 10.0= 11.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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if Version is 8.1, 9.0, 10.0, or 11.0 exactly
-
Confirm device is SamsungGo to Settings > About Phone > Manufacturer or Model name, or run 'adb shell getprop ro.product.manufacturer'Affected if Manufacturer shows as Samsung
-
Verify Bluetooth is enabledCheck Settings > Bluetooth is turned on, or run 'adb shell settings get global bluetooth_on' returning 1Affected if Bluetooth is enabled on the device
The device is affected if it is a Samsung device running Android 8.1, 9.0, 10.0, or 11.0 with Bluetooth enabled, as the improper access control in Samsung Bluetooth APIs allows any app to retrieve sensitive Bluetooth details without proper permission validation.
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 Samsung SMR (Security Maintenance Release) September 2021 Release 1 or later via system updates. Organizations should ensure mobile device management (MDM) policies enforce timely security patches on managed devices.
Samsung SMR Sep-2021 Release 1 (or later)
- Check your Samsung device model and current Android version
- Navigate to Settings > About Phone > Software Update on your device
- Ensure your device is connected to Wi-Fi and has sufficient battery
- Check for and install the latest Samsung Security Maintenance Release (SMR)
- Specifically look for and apply the SMR September 2021 update or later
- After updating, verify the Bluetooth permission behavior has been restricted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Testing2.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 $2,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25453 — 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-25453 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