LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25369: An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive...

An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive kernel information to userspace.

MediumCVSS 6.2Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Samsung Mobile flaw lets information meant to stay inside the kernel become visible to userspace through insufficient access control on the sec_log file. The direct impact is sensitive information disclosure, not system takeover. Business urgency is elevated because CISA lists CVE-2021-25369 in KEV, meaning known exploitation is documented.

Executive priority

Treat this as a high-priority mobile fleet cleanup item because KEV status changes the risk profile despite a medium CVSS score. Focus on patch compliance and retiring legacy Samsung devices that cannot be updated.

Technical view

CVE-2021-25369 is CWE-200 improper exposure of sensitive information in Samsung Mobile Devices running O(8.x), P(9.0), and Q(10.0) before SMR MAR-2021 Release 1. CVSS 3.1 is 6.2: local attack vector, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is most likely on corporate-managed or BYOD Samsung Android devices on O(8.x), P(9.0), or Q(10.0) that have not received SMR MAR-2021 Release 1 or later. Unsupported legacy devices are the highest concern.

Exploitation context

CISA KEV status supports known exploitation. The provided sources do not identify exploit campaigns, affected device models, attacker tooling, or indicators. The CVSS vector indicates local exploitation with no required privileges or user interaction.

Researcher notes

The source bundle is sparse: it names sec_log access control, kernel information exposure, affected Android generations, CVSS, and Samsung’s March 2021 security maintenance release. It does not provide exploit mechanics, affected model granularity, forensic indicators, or detailed mitigations beyond vendor update guidance.

Mitigation direction

  • Apply Samsung SMR MAR-2021 Release 1 or later where available.
  • Prioritize corporate and privileged-user Samsung devices for update verification.
  • Remove or replace unsupported affected devices that cannot receive the Samsung fix.
  • Use MDM policy to block outdated Android security patch levels.
  • Check Samsung advisories for device-specific update availability.

Validation and detection

  • Inventory Samsung devices by OS version and Android security patch level.
  • Confirm affected devices are not on O(8.x), P(9.0), or Q(10.0) before SMR MAR-2021 Release 1.
  • Review MDM compliance reports for stale or unsupported Samsung devices.
  • Verify security update status against Samsung Mobile guidance.
  • Document exceptions where devices cannot be patched and require replacement.
Prepared
Confidence
high
Sources
5

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-25369 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.2 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesO(8.x), P(9.0), Q(10.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.