dbcve.org
AndroidOperating system · Google

CVE-2021-25361

HIGH · 8.8 CVSS v3.1 Published 2021-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
An improper access control vulnerability in stickerCenter prior to SMR APR-2021 Release 1 allows local attackers to read or write arbitrary files of system process via untrusted applications.

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

An improper access control vulnerability in the stickerCenter application on Samsung mobile devices allows untrusted local applications to read or write arbitrary files within the system process context. This enables local privilege escalation or sensitive data exfiltration.

MitigationUpdate stickerCenter to SMR APR-2021 Release 1 or later to obtain the patched version with proper access controls.

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:= 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 Samsung running Android 10 or 11
    Go to Settings > About Phone and verify the manufacturer is Samsung and Android version is 10.0 or 11.0
    Affected if Device is not Samsung or Android version is not 10.0 or 11.0 - then not affected by this specific CVE
  2. Check if stickerCenter application is installed
    Navigate to Settings > Apps and search for 'stickerCenter' or 'Sticker Center'. Alternatively, use ADB command: adb shell pm list packages | grep -i sticker
    Affected if stickerCenter app is not installed - then not affected by this vulnerability
  3. Determine stickerCenter version
    In Settings > Apps > stickerCenter > App info, note the version name/version number. If using ADB: adb shell dumpsys package com.samsung.android.stickercenter (or the actual package name)
    Affected if Version is earlier than SMR APR-2021 Release 1 patched version - device is vulnerable if the app is present on Android 10 or 11
  4. Verify the app has sensitive file access permissions
    Review stickerCenter app permissions in Settings > Apps > stickerCenter > Permissions. Specifically check for Storage or Files and Media permissions that allow broad file system access
    Affected if App has broad storage permissions and version is unpatched - the improper access control vulnerability is present

A Samsung device running Android 10.0 or 11.0 with the stickerCenter app installed and version earlier than SMR APR-2021 Release 1 is affected by this improper access control vulnerability.

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

Update stickerCenter to SMR APR-2021 Release 1 or later to obtain the patched version with proper access controls.

Recommended fix High confidence

SMR APR-2021 Release 1 (April 2021 Samsung Security Patch)

  1. Navigate to Settings > About Phone on the Samsung device
  2. Check the Android version to confirm it is 10.0 or 11.0
  3. Navigate to Settings > Software Update
  4. Tap 'Download and Install' to check for available updates
  5. Update to the April 2021 Samsung security patch (SMR APR-2021 Release 1) or later
  6. Verify the update was applied by checking Settings > About Phone > Software Information > Security patch level
Caveat Standard Android update risks apply - ensure backup of important data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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