LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25397: An improper access control vulnerability in TelephonyUI prior to SMR MAY-2021 Release 1 allows local attack...

An improper access control vulnerability in TelephonyUI prior to SMR MAY-2021 Release 1 allows local attackers to write arbitrary files of telephony process via untrusted applications.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Samsung fixed a TelephonyUI access-control flaw in its May 2021 security maintenance release. On affected Samsung Mobile Devices running Android 9, 10, or 11, a malicious local app could write arbitrary files as the telephony process, risking device integrity and some service availability.

Executive priority

Treat this as a moderate mobile fleet hygiene issue, not an emergency based on the supplied evidence. Prioritize patch verification for Samsung devices that handle sensitive communications or are allowed to install unmanaged apps.

Technical view

CVE-2021-25397 is CWE-926 improper access control in TelephonyUI before SMR MAY-2021 Release 1. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L, meaning local attack, low complexity, no privileges, no user interaction, high integrity impact, and low availability impact.

Likely exposure

Exposure is most relevant to unmanaged or slow-patched Samsung Mobile Devices on Android P, Q, or R that predate Samsung SMR MAY-2021 Release 1. Enterprise risk depends on device inventory, patch level visibility, and exposure to untrusted app installation.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The described attacker is local and can act through an untrusted application, so the practical scenario is malicious app presence on an affected Samsung device.

Researcher notes

The source bundle attributes arbitrary telephony-process file write to improper TelephonyUI access control before Samsung’s May 2021 release. Public evidence supplied here is sufficient for affected platform and patch direction, but not for model-specific impact, exploit maturity, or in-the-wild activity.

Mitigation direction

  • Update affected Samsung devices to SMR MAY-2021 Release 1 or later.
  • Prioritize corporate-managed Samsung devices running Android 9, 10, or 11.
  • Restrict untrusted app installation through MDM or enterprise app controls.
  • Review Samsung’s advisory for device-specific patch availability and status.
  • Retire or isolate devices that cannot receive the May 2021 security maintenance release.

Validation and detection

  • Inventory Samsung Mobile Devices and record Android version and security patch level.
  • Flag Android 9, 10, or 11 devices below SMR MAY-2021 Release 1.
  • Confirm TelephonyUI-related Samsung security updates are applied where available.
  • Check MDM controls limiting sideloading and untrusted application sources.
  • Document unsupported devices requiring compensating controls or replacement.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-926: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25397 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L2.54.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2021-25397Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesP(9.0), Q(10.0), R(11.0)Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-926 · source CWE mapping

Improper Export of Android Application Components

Improper Export of Android Application Components represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.