dbcve.org
AndroidOperating system · Samsung

CVE-2023-42565

MEDIUM · 6.7 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 14.0 or later.
See remediation →
69/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 input validation vulnerability in Smart Clip prior to SMR Dec-2023 Release 1 allows local attackers with shell privilege to execute arbitrary code.

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 input validation vulnerability in Samsung Smart Clip (mobile component) prior to SMR Dec-2023 Release 1 allows local attackers with shell-level privileges to execute arbitrary code via crafted input that bypasses validation checks.

MitigationApply SMR Dec-2023 Release 1 or later firmware update to patch the improper input validation vulnerability; for managed device fleets, ensure all affected devices receive the vendor patch.

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:>= 13.0, < 14.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 device is a Samsung Android phone or tablet
    Check the device settings: go to Settings > About Phone > Manufacturer should show 'Samsung' and the device should be running Android OS, not another OS.
    Affected if Device is not made by Samsung or does not run Android, then not affected by this specific vulnerability.
  2. Identify the installed Android version
    Navigate to Settings > About Phone > Android Version. Record the exact version number displayed (e.g., 13.0, 13.0.0, 14.0, 14.0.1).
    Affected if The Android version is 13.0 (any 13.0.x build) or exactly 14.0, then the device falls within the affected version range.
  3. Check if Smart Clip component is present on the device
    Using a file manager or ADB shell, look for the Smart Clip application or service. Common paths include /system/app/SmartClip or check the package list via 'pm list packages | grep smartclip' in ADB shell.
    Affected if The Smart Clip component is not installed or not found, then the vulnerability cannot be exploited on this device.
  4. Verify shell-level access availability
    Determine if ADB debugging is enabled or if a root shell can be obtained. Run 'adb shell' or check if the device has root privileges via 'su' command.
    Affected if The device lacks shell-level access (no ADB, no root), the attack vector for this specific CVE is not directly exploitable by a local attacker.

Your Samsung Android device is affected if it runs Android version 13.0 or 14.0 AND has the Smart Clip component installed AND has shell-level access available to a local attacker.

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
Upgrade available Upgrade to 14.0 or later
Fixed in 14.0
Interim mitigation

Apply SMR Dec-2023 Release 1 or later firmware update to patch the improper input validation vulnerability; for managed device fleets, ensure all affected devices receive the vendor patch.

Recommended fix High confidence

SMR Dec-2023 Release 1 (December 2023 Security Maintenance Release)

  1. Check your device for system updates in Settings > Software update
  2. Download and install the December 2023 security update (SMR Dec-2023 Release 1)
  3. Restart the device after the update completes
  4. Verify the security patch level is December 2023 or later in 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
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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