LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25392: Improper protection of backup path configuration in Samsung Dex prior to SMR MAY-2021 Release 1 allows loca...

Improper protection of backup path configuration in Samsung Dex prior to SMR MAY-2021 Release 1 allows local attackers to get sensitive information via changing the path.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects Samsung Dex on Samsung mobile devices before the May 2021 Samsung Mobile Security Release. A local attacker could change a backup path setting and obtain sensitive information. It is not described as remotely exploitable, and the supplied sources do not show active exploitation.

Executive priority

Treat this as a patch compliance issue, not an emergency incident by default. The business risk is sensitive information exposure from local access on outdated Samsung devices, so priority depends on fleet size, device age, and whether corporate data is present.

Technical view

Samsung Dex had improper protection of backup path configuration before SMR MAY-2021 Release 1. The CVSS vector is local, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact only. Samsung lists affected Android P, Q, and R Samsung mobile devices.

Likely exposure

Exposure is limited to Samsung mobile devices running affected Samsung Dex builds before SMR MAY-2021 Release 1 on Android 9, 10, or 11. Risk is most relevant for unmanaged or legacy Samsung fleets that may not have received 2021 security updates.

Exploitation context

The source bundle reports local attack conditions and sensitive information exposure through path changes. It does not cite CISA KEV listing, public active exploitation, or remote exploitation. Evidence is limited to the CVE description, Samsung advisory, and linked research reference.

Researcher notes

The vulnerability maps to CWE-200 and has CVSS 3.1 score 4.0. The available evidence does not identify specific files, data types, proof-of-concept status, or fixed build numbers beyond Samsung SMR MAY-2021 Release 1.

Mitigation direction

  • Apply Samsung SMR MAY-2021 Release 1 or later to affected devices.
  • Prioritize Samsung devices running Android 9, 10, or 11 without current security updates.
  • Use MDM inventory to identify unsupported or noncompliant Samsung devices.
  • Check Samsung guidance before assuming alternative mitigations exist.
  • Retire or isolate devices that cannot receive vendor security updates.

Validation and detection

  • Inventory Samsung mobile devices and record Android version and security patch level.
  • Confirm Samsung Dex-enabled devices are at or beyond the May 2021 security release.
  • Review MDM compliance reports for devices missing Samsung security maintenance releases.
  • Validate exceptions for legacy devices with compensating controls or retirement plans.
  • Do not use exploit testing unless authorized and based on vendor-safe procedures.
Prepared
Confidence
medium
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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-25392 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
4 (3.1)
Known Exploited
No
Published

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

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
4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N2.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.