CVE-2024-20808
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 · uneditedImproper access control vulnerability in Nearby device scanning prior version 11.1.14.7 allows local attacker to access data.
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 confidenceAn improper access control vulnerability exists in the Nearby device scanning feature of an application (prior to version 11.1.14.7) that allows a local attacker to access data they should not have permission to view. The vulnerability stems from insufficient authorization checks during the device scanning process, enabling a local user to bypass access controls and retrieve sensitive information about nearby devices or their associated data.
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< 11.1.14.7CVSS 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.
-
Identify Nearby Device Scanning componentLocate the Samsung Nearby Device Scanning feature in the device settings or application manager. This is typically found under Settings > Connections > Nearby Device Scanning on Samsung devices, or as a system component named similarly in the apps list.Affected if The feature or application is present on the device
-
Determine the installed versionAccess the app info or version details for the Nearby Device Scanning component. In Android, this can be found in Settings > Apps > Nearby Device Scanning (or similar naming) > App info, or via ADB using 'adb shell dumpsys package | grep -i nearby' to find package details and version.Affected if The version cannot be determined or shows as a pre-11.1.14.7 release
-
Compare version against affected rangeReview the displayed version number and compare it to the affected version range: any version prior to 11.1.14.7. Check both the major.minor.patch format and any build numbers if visible.Affected if Installed version is less than 11.1.14.7 (e.g., 11.1.14.6, 11.1.13.x, 10.x, etc.)
-
Verify if Nearby Device Scanning is enabledCheck the current state of the Nearby Device Scanning toggle in Settings > Connections > Nearby Device Scanning. Also check if any scanning activity has occurred recently by reviewing notification history or the feature's usage log if available.Affected if The feature is currently turned ON or has been used recently, making it actively exploitable
The device is affected if it runs Samsung Nearby Device Scanning with a version lower than 11.1.14.7 and has the feature enabled or has been used.
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 · scoped11.1.14.7
Upgrade to version 11.1.14.7 or later which contains the proper access control fixes. Until patched, restrict device access to trusted users and monitor for unauthorized scanning attempts.
Nearby Device Scanning version 11.1.14.7 or later
- Upgrade the Nearby Device Scanning application to version 11.1.14.7 or later
- Verify the upgrade was successful by checking the application version in device settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20808 — 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-20808 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