CVE-2023-30654
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 SLocationService prior to SMR Aug-2023 Release 1 allows local attacker to update fake location.
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 · high confidenceImproper access control in SLocationService on Samsung mobile devices prior to the August 2023 SMR allows a local attacker to inject or update false location data. This is a medium-severity (CVSS 5.5) vulnerability requiring local device access.
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.0= 12.0= 13.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 the device manufacturerCheck Settings > About Phone > Manufacturer or look for Samsung brandingAffected if Device is not a Samsung mobile device (vulnerability only affects Samsung devices)
-
Check the Android OS versionGo to Settings > About Phone > Android versionAffected if Android version is 11.0, 12.0, or 13.0 (these are the affected versions)
-
Check the Samsung SMR (Security Maintenance Release) versionGo to Settings > About Phone > Software information > Samsung security patch levelAffected if Security patch level is earlier than August 2023 (SMR Aug-2023 Release 1 or later contains the fix)
-
Verify SLocationService component presenceCheck device settings or use adb shell to list services: service list | grep -i slocationAffected if SLocationService is present and running on the device (vulnerability is in this component)
-
Confirm location permissions and accessReview Settings > Location > App permissions to see which apps can access location servicesAffected if Apps without proper authorization can access or modify location data through SLocationService
A user is affected if they are on a Samsung Android device running version 11.0, 12.0, or 13.0 with a Samsung security patch level earlier than August 2023.
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 Samsung SMR August-2023 Release 1 or later security update, which contains the fix for the improper access control in SLocationService.
Samsung SMR Aug-2023 Release 1 or later
- Go to Settings on the Samsung Android device
- Navigate to Software update
- Select Download and install to check for and install the latest Samsung security update
- Ensure the device updates to SMR Aug-2023 Release 1 or later which contains the fix for CVE-2023-30654
- Verify the security patch level in Settings > About phone > Software information > Security patch level shows August 2023 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30654 — 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-2023-30654 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