dbcve.org
AndroidOperating system · Samsung

CVE-2024-20895

MEDIUM · 5.5 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 →
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 in Dar service prior to SMR Jul-2024 Release 1 allows local attackers to bypass restriction for calling SDP features.

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

This is a local privilege escalation vulnerability in Samsung's Dar service (part of Samsung's Android implementation). The service has improper access control that allows local attackers to bypass security restrictions and call SDP (Samsung DeX Protocol or similar Samsung Desktop features) that should be restricted. A local malicious app or process could potentially invoke privileged SDP functions without proper authorization.

MitigationApply the Samsung SMR (Security Maintenance Release) July 2024 update or later, which contains the fix for this improper access control in the Dar service. Organizations should ensure managed Samsung devices are receiving monthly security updates.

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

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

  1. Verify Android version is affected
    Check the device's Android version in Settings > About Phone > Android version. Confirm the version is 12.0, 13.0, or 14.0.
    Affected if The device runs Android 12.0, 13.0, or 14.0 - only these versions are in the affected range.
  2. Confirm Dar service presence
    Using ADB or a diagnostic tool, check if the Samsung 'dar' service is installed on the device. On Samsung devices, this can be verified via 'dumpsys' or checking the system service list.
    Affected if The Dar service is present and running on the device, as this is the vulnerable component.
  3. Identify if SDP/Dex features are configured
    Check if Samsung DeX or SDP (Samsung Desktop Protocol) features are enabled on the device. This can be found in Settings > Samsung DeX or through system configuration files.
    Affected if Samsung DeX or SDP features are enabled or have been used on the device, creating the attack surface for the vulnerability.
  4. Check security patch level
    Verify the installed security patch level in Settings > About Phone > Security patch level. Compare against the July 2024 SMR release date.
    Affected if The security patch level is earlier than July 2024, indicating the fix has not been applied.

A device is affected if it runs Android 12.0, 13.0, or 14.0, has the Dar service present, 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 the Samsung SMR (Security Maintenance Release) July 2024 update or later, which contains the fix for this improper access control in the Dar service. Organizations should ensure managed Samsung devices are receiving monthly security updates.

Recommended fix Moderate confidence

SMR Jul-2024 Release 1 or later

  1. Check your current Android version by going to Settings > About Phone > Android version
  2. Go to Settings > Software update
  3. Tap on Download and install to check for available updates
  4. Download and install the SMR (Samsung Monthly Release) Jul-2024 or later
  5. After installation, verify the update was applied by checking Settings > Software update > Download history

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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