dbcve.org
AndroidOperating system · Samsung

CVE-2024-20857

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 vulnerability in startListening of CocktailBarService prior to SMR May-2024 Release 1 allows local attackers to access information of current application.

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 confidence

This is an improper access control vulnerability in Samsung's CocktailBarService (a system UI service) specifically in the startListening function. The flaw allows local attackers to access information from the current application without proper authorization. It affects Samsung devices on Android versions prior to the May-2024 Security Maintenance Release (SMR).

MitigationApply the Samsung SMR May-2024 Release 1 or later security patch, which contains the proper access control fixes for CocktailBarService. Organizations should ensure enterprise device fleets are updated through their MDM/EMM platforms.

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
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 checks

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

  1. Confirm device is a Samsung Android device
    Check the device manufacturer and model through Settings > About Phone > Manufacturer or use 'getprop ro.product.manufacturer' via ADB
    Affected if Device is not manufactured by Samsung
  2. Check Android version
    Navigate to Settings > About Phone > Android version or use 'getprop ro.build.version.release' via ADB
    Affected if Android version is 12, 13, or 14 (versions prior to the fix)
  3. Check Samsung Security Patch Level (SPL)
    Navigate to Settings > About Phone > Software information > Security patch level or use 'getprop ro.build.version.security_patch' via ADB
    Affected if Security patch level is earlier than May-2024 SMR (the date format is typically YYYY-MM-DD, so dates before 2024-05)
  4. Verify CocktailBarService is present
    Check for the service via ADB command 'dumpsys' or verify the Samsung One UI system UI package is installed - the service is part of Samsung's system UI (com.samsung.android.app.cocktailbarservice)
    Affected if CocktailBarService is present and running on an unpatched device

A Samsung Android device on version 12, 13, or 14 with a Security Patch Level earlier than May-2024 is affected by this improper access control vulnerability in CocktailBarService.

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 the Samsung SMR May-2024 Release 1 or later security patch, which contains the proper access control fixes for CocktailBarService. Organizations should ensure enterprise device fleets are updated through their MDM/EMM platforms.

Recommended fix High confidence

SMR May-2024 Release 1 (Android Security Patch Level May 2024 or later)

  1. Check the current Android security patch level on the device in Settings > About Phone > Software Information > Security patch level
  2. Verify if the device has received the SMR May-2024 Release 1 security update or later
  3. If not updated, check for system/software updates in Settings > Software Update and install any available updates
  4. Alternatively, contact the device manufacturer or carrier for the specific security patch update containing the SMR May-2024 Release 1 fix
  5. Ensure the CocktailBarService is not exposed to untrusted local applications through device administration or accessibility service policies

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20857 — 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-20857 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