Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Nov 2022.
AndroidOperating system · Samsung

CVE-2021-25337

HIGH · 7.1 CVSS v3.1 Published 2021-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
In the wild 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 clipboard service in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows untrusted applications to read or write certain local files.

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 clipboard service on mobile devices. The flaw allows untrusted or malicious applications to bypass normal Android sandboxing and read or write certain local files that should be protected. This could enable data theft or manipulation of sensitive files through clipboard interactions.

MitigationApply the Samsung SMR Mar-2021 Release 1 or later security update to affected devices. For enterprise environments, ensure MDM/EMM solutions are deployed to identify and remediate unpatched Samsung devices.

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:= 9.0= 10.0= 11.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
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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. Confirm device is a Samsung Android device
    Check Settings > About Phone > Model number to verify the manufacturer is Samsung.
    Affected if Non-Samsung devices are not affected by this vulnerability
  2. Check the Android version
    Navigate to Settings > About Phone > Android version and note the major version number.
    Affected if The device runs Android 9, Android 10, or Android 11 (the affected versions)
  3. Check the Samsung security patch level
    Go to Settings > About Phone > Security patch level and note the date of the last Samsung security update.
    Affected if The security patch level is earlier than March 2021, meaning the SMR Mar-2021 Release 1 update has not been applied
  4. Verify clipboard service is accessible
    Check if Samsung clipboard functionality is available on the device. On affected versions, the clipboard service can be accessed by any app, allowing potential file access.
    Affected if The Samsung clipboard service is present and can be invoked by applications on the device

A Samsung device running Android 9, 10, or 11 with a security patch level earlier than March 2021 is likely affected by this improper access control vulnerability in the clipboard service.

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 Mar-2021 Release 1 or later security update to affected devices. For enterprise environments, ensure MDM/EMM solutions are deployed to identify and remediate unpatched Samsung devices.

Recommended fix High confidence

SMR Mar-2021 Release 1 or later

  1. 1. Go to Settings on the Samsung Android device
  2. 2. Navigate to 'Software update' or 'System updates'
  3. 3. Tap on 'Download and install' or 'Check for updates'
  4. 4. Ensure the device downloads and installs the March 2021 Samsung security update (SMR Mar-2021 Release 1) or later
  5. 5. Verify the update was installed successfully by checking the Samsung security patch level in Settings > About phone > Software information
Caveat Minimal risk - standard security patch update; ensure device has sufficient battery before updating

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

Fix this in Android Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-25337 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-25337 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