CVE-2024-20809
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 confidenceImproper access control in the Nearby device scanning feature of a mobile application (versions prior to 11.1.14.7) allows a local attacker to access data they should not have permission to view. This suggests the scanning function did not properly validate user permissions before returning device or discovery 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 Samsung Nearby Device Scanning applicationLocate the Samsung application that contains Nearby Device Scanning functionality - this is typically found in Samsung system apps on Galaxy devices (commonly part of Samsung Account, Samsung Cloud, or companion device scanning features). Check the installed applications list for Samsung-branded apps that include device discovery or nearby sharing capabilities.Affected if The application is present and has Nearby Device Scanning functionality enabled.
-
Check application versionAccess the app settings for the Samsung application containing Nearby Device Scanning. Navigate to the app's info section (Settings > Apps > [Nearby Device Scanning app]) and record the version number shown. Compare this version against the fixed version 11.1.14.7.Affected if The installed version is lower than 11.1.14.7 (for example, 11.1.14.6, 11.1.10.3, etc.).
-
Verify Nearby Device Scanning is enabledIn the Samsung device settings, locate the Nearby Device Scanning or device discovery feature (typically under Settings > Connections > Nearby Device Scanning, or Settings > Privacy > Nearby Device Scanning). Check whether the feature toggle is turned ON or if the feature has been used recently.Affected if The Nearby Device Scanning feature is currently enabled or has been recently used on the device.
-
Review permission grantsCheck what permissions the Nearby Device Scanning application has been granted. Go to Settings > Apps > [Nearby Scanning app] > Permissions. Look for permissions related to location, Bluetooth, Wi-Fi, contacts, or storage that may be exploited due to improper access control.Affected if The application has been granted elevated permissions (especially location, contacts, or storage) and runs on a vulnerable version.
You are affected if your Samsung device has a Nearby Device Scanning application version lower than 11.1.14.7 and the scanning feature is or was enabled, as the improper access control could allow unauthorized data access.
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 for the Nearby device scanning functionality.
11.1.14.7 or later for Nearby Device Scanning
- Ensure your Samsung device is connected to Wi-Fi or cellular network
- Go to Settings > Software Update on your Samsung device
- Tap 'Download and install' to check for available updates
- Loculate and install the update that includes version 11.1.14.7 or later for Nearby Device Scanning
- After installation, verify the Nearby Device Scanning app has been updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20809 — 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-20809 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