CVE-2024-20858
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 setCocktailHostCallbacks 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 confidenceThis is an improper access control vulnerability in Samsung's CocktailBarService (specifically the setCocktailHostCallbacks function) that allows local attackers to access information about the current application. The vulnerability exists in Samsung Mobile Device (SMR) versions prior to the May-2024 Release 1 patch. A local attacker could exploit this to gather sensitive application information without proper authorization.
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= 12.0= 13.0= 14.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
- 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.
-
Check Samsung SMR versionGo to Settings > About Phone > Software Information and look for the SMR (Samsung Maintenance Release) number. Compare it against the May-2024 Release 1 patch level.Affected if The SMR version is earlier than the May-2024 Release 1 patch (e.g., April-2024 or earlier SMR).
-
Confirm Android OS versionGo to Settings > About Phone > Android version to verify the installed Android OS version.Affected if The device is running Android 12.0, 13.0, or 14.0 and has not received the May-2024 security update.
-
Check for CocktailBarService presenceExamine installed Samsung system services or packages for the presence of CocktailBarService or related CocktailBar components in the system.Affected if The CocktailBarService component exists on the device and the SMR version is unpatched.
A device is affected if it runs Android 12.0, 13.0, or 14.0 with a Samsung SMR version earlier than the May-2024 Release 1 patch.
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 May-2024 Release 1 security update or later to affected Samsung mobile devices to patch the improper access control vulnerability in CocktailBarService.
SMR May-2024 Release 1
- Check your current Android security patch level in Settings > About Phone > Software Information > Security patch level
- Determine if your Samsung device model is scheduled to receive the SMR May-2024 Release 1 update
- Navigate to Settings > Software Update and check for available updates
- Download and install the May-2024 security update when available for your device model
- Verify the security patch level has been updated to May-2024 or later after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20858 — 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-20858 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