dbcve.org
AndroidOperating system · Samsung

CVE-2024-20888

HIGH · 7.8 CVSS v3.1 Published 2024-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Improper access control in OneUIHome prior to SMR Jul-2024 Release 1 allows local attackers to launch privileged activities. User interaction is required for triggering this vulnerability.

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 confidence

Improper access control in Samsung's OneUIHome (the TouchWiz/OneUI launcher) prior to the July 2024 security patch allows a local attacker to launch privileged activities through the home screen application. The vulnerability requires user interaction to trigger, likely involving social engineering to get a victim to launch or interact with a malicious component that then exploits the improper authorization checks in the launcher.

MitigationApply Samsung's SMR Jul-2024 Release 1 or later security update which contains the access control fix. Organizations should enforce mobile device management policies to ensure timely security patch deployment.

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
AndroidOperating system
Affected:= 12.0= 13.0= 14.0

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Samsung Android device
    Check if the device is a Samsung phone or tablet by reviewing the device model in Settings > About Phone > Model Number
    Affected if Device is not a Samsung product - this vulnerability only affects Samsung devices
  2. Verify Android version
    Go to Settings > About Phone > Android Version and confirm the exact version number
    Affected if Android version is 12.0, 13.0, or 14.0 - these are the affected versions listed
  3. Identify default launcher
    Check which launcher app is set as default: go to Settings > Apps > Default apps > Home screen and verify if OneUIHome (com.sec.android.app.launcher) is selected
    Affected if OneUIHome is the default home screen launcher - the vulnerability exists in this specific launcher
  4. Check security patch level
    Go to Settings > About Phone > Security patch level and note the date of the installed Samsung security update
    Affected if Security patch level is earlier than July 2024 - the fix was released in SMR Jul-2024 Release 1

A Samsung device is affected if it runs Android 12.0, 13.0, or 14.0 with OneUIHome as the default launcher and has a security patch level before July 2024.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung's SMR Jul-2024 Release 1 or later security update which contains the access control fix. Organizations should enforce mobile device management policies to ensure timely security patch deployment.

Recommended fix High confidence

SMR Jul-2024 Release 1

  1. Check the current Android version on the Samsung device (Settings > About Phone > Android version)
  2. Go to Settings > Software update and tap 'Download and install'
  3. Ensure the device connects to a stable Wi-Fi network and has sufficient battery (50%+)
  4. Apply the July 2024 security update (SMR Jul-2024 Release 1) when prompted
  5. After installation completes, verify the patch was applied by checking Settings > About Phone > Software information > Security patch level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20888 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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