CVE-2021-25337 — Samsung Mobile Devices Improper Access Control Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 2.8% (30-day exploitation probability)+13
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: Nov 29, 2022 — passed 1416 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Samsung Android, Samsung Mobile Samsung Mobile Devices).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Samsung | Android |
version 10.0-smr-jan-2021-r1version 9.0-smr-oct-2019-r1version 9.0-smr-oct-2020-r1version 9.0-smr-sep-2019-r1version 9.0-smr-sep-2020-r1version 10.0-smr-apr-2020-r1version 10.0-smr-aug-2020-r1version 10.0-smr-dec-2019-r1 and 40 moreversion 10.0-smr-dec-2020-r1version 10.0-smr-feb-2020-r1version 10.0-smr-feb-2021-r1version 10.0-smr-jan-2020-r1version 9.0-smr-apr-2020-r1version 10.0-smr-jul-2020-r1version 10.0-smr-jun-2020-r1version 10.0-smr-mar-2020-r1version 10.0-smr-may-2020-r1version 10.0-smr-nov-2019-r1version 10.0-smr-nov-2020-r1version 10.0-smr-oct-2020-r1version 10.0-smr-sep-2020-r1version 11.0-smr-dec-2020-r1version 11.0-smr-feb-2021-r1version 11.0-smr-jan-2021-r1version 9.0-smr-nov-2020-r1version 9.0-smr-apr-2019-r1version 9.0-smr-aug-2019-r1version 9.0-smr-aug-2020-r1version 9.0-smr-dec-2018-r1version 9.0-smr-dec-2019-r1version 9.0-smr-dec-2020-r1version 9.0-smr-feb-2019-r1version 9.0-smr-feb-2020-r1version 9.0-smr-feb-2021-r1version 9.0-smr-jan-2019-r1version 9.0-smr-jan-2020-r1version 9.0-smr-jan-2021-r1version 9.0-smr-jul-2019-r1version 9.0-smr-jul-2020-r1version 9.0-smr-jun-2019-r1version 9.0-smr-jun-2020-r1version 9.0-smr-mar-2019-r1version 9.0-smr-mar-2020-r1version 9.0-smr-may-2019-r1version 9.0-smr-may-2020-r1version 9.0-smr-nov-2018-r1version 9.0-smr-nov-2019-r1version 9.0-smr-oct-2018-r1 |
Vulnerable | NIST National Vulnerability Database |
| Samsung Mobile | Samsung Mobile Devices | ≥ Selected P(9.0), Q(10.0), R(11.0) and < SMR Mar-2021 Release 1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 1.8 | 5.2 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.4 | CVSS 3.1 | Medium | 1.8 | 2.5 | mobile.security@samsung.com via NIST National Vulnerability Database |
| 4.4 | CVSS 3.1 | Medium | — | — | Samsung Mobile via CVE Program (cve.org) e CISA ADP |
| 5.8 | CVSS 2.0 | Medium | 8.6 | 4.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- CVE-2021-25337 ★ 1 Apr 17, 2026
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 2.81%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Hunt retroactively in logs from before Nov 8, 2022 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · samsung/android
- CVSS changed · 4.4 → 7.1
- Source status changed · Published → Analyzed
- Record published
- Affected products added · samsung mobile/samsung mobile devices
- CVSS changed · 4.4
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2022
- Added to CISA KEV catalog
- 2021
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-21126 Improper input validation in getting cover image in libsimba.heifdec.media.samsung.so prior to... 3d
- High CVE-2026-21125 Improper input validation in parsing sheifd in libsimba.heifdec.media.samsung.so prior to SMR Oct... 3d
- Medium CVE-2026-21119 Out-of-bounds read and write in lib_sag_ai_sound_sep_v2.00.so prior to SMR Oct-2026 Release 1... 3d
- Medium CVE-2026-21118 Improper access control in DownloadProvider prior to SMR Oct-2026 Release 1 allows local... 3d
- Medium CVE-2026-21117 Improper access control in CocktailBarService prior to SMR Oct-2026 Release 1 allows local... 3d
- Medium CVE-2026-21121 Improper handling of insufficient permission in CmcCore prior to SMR Oct-2026 Release 1 allows... 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2021-25337 is "Samsung Mobile Devices Improper Access Control Vulnerability", rated High. It affects Android (Samsung); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.1 describes technical severity. EPSS 2.81% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.