CVE-2023-30713
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 privilege management vulnerability in FolderLockNotifier in One UI Home prior to SMR Sep-2023 Release 1 allows local attackers to change some settings of the folder lock.
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 confidenceThis is an improper privilege management vulnerability in Samsung's One UI Home application (specifically the FolderLockNotifier component). The flaw allows local attackers to bypass authorization checks and modify settings for the folder lock feature, potentially exposing protected content without proper authentication.
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.
-
Check Samsung Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version is 11.0, 12.0, or 13.0 exactly (the = notation indicates exact versions)
-
Check One UI Home application versionGo to Settings > Apps > One UI Home > App info, or run 'dumpsys package com.samsung.android.app.launcher' via ADB shellAffected if One UI Home version is unpatched and matches the Sep-2023 release 1 or earlier baseline for your Android version
-
Verify FolderLockNotifier component existsRun 'dumpsys package com.samsung.android.app.launcher' and look for activity/component named 'FolderLockNotifier' or check if the package exports this componentAffected if FolderLockNotifier component is exported/enabled in the One UI Home package without proper permission checks
-
Check folder lock feature configurationNavigate to Samsung launcher settings > Folder lock or run 'content query --uri content://com.samsung.android.app.launcher.settings/folderlock' via ADBAffected if Folder lock feature is configured or enabled on the device, exposing the attack surface
Device is affected if it runs Samsung Android 11.0, 12.0, or 13.0 with an unpatched One UI Home version containing the vulnerable FolderLockNotifier component and with folder lock feature available or enabled.
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 Sep-2023 Release 1 or later firmware update to One UI Home, which contains the proper privilege enforcement fixes for the FolderLockNotifier component.
SMR Sep-2023 Release 1 (One UI Home)
- Open Settings on the Samsung device
- Navigate to About Phone > Software Information or Settings > Software Update
- Check the current One UI Home version
- Ensure the device is updated to SMR Sep-2023 Release 1 or later
- If update is not available, check for Samsung security updates in Settings > Security update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30713 — 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-30713 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