LiveActive security incident?Get immediate response
CVE Record

CVE-2023-21441: Insufficient Verification of Data Authenticity vulnerability in Routine prior to versions 2.6.30.6 in Andro...

Insufficient Verification of Data Authenticity vulnerability in Routine prior to versions 2.6.30.6 in Android Q(10), 3.1.21.10 in Android R(11) and 3.5.2.23 in Android S(12) allows local attacker to access protected files via unused code.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Samsung Routine flaw can let someone with local attack path and user interaction access protected files on affected Samsung Android devices. It is high severity because successful exploitation could expose or alter sensitive data, but sources describe high complexity and local access, limiting broad internet-scale risk.

Executive priority

Treat as a high-priority mobile patching item for Samsung fleets, especially sensitive-user devices. The business urgency is data protection rather than internet-wide compromise; sources do not support claims of active exploitation.

Technical view

CVE-2023-21441 is CWE-345 insufficient verification of data authenticity in Samsung Mobile Routine before fixed versions for Android 10, 11, and 12. The CVSS 3.1 vector is AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N, indicating local attack, high complexity, user interaction, and high confidentiality and integrity impact.

Likely exposure

Likely exposure is Samsung Android Q (10), R (11), and S (12) devices running Routine below the fixed versions. The provided sources do not identify exposure on non-Samsung products or remote network attack surface.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates a local attacker and required user interaction, so risk is most relevant for compromised, shared, or physically accessible devices.

Researcher notes

Evidence is limited to the CVE record and Samsung advisory metadata. The description mentions access to protected files via unused code but does not provide technical root-cause detail, affected model list, exploit maturity, or operational indicators.

Mitigation direction

  • Update Routine to 2.6.30.6 or later on Android 10 devices.
  • Update Routine to 3.1.21.10 or later on Android 11 devices.
  • Update Routine to 3.5.2.23 or later on Android 12 devices.
  • Apply the relevant Samsung February 2023 security maintenance release where available.
  • Check Samsung guidance for device-specific update availability.

Validation and detection

  • Inventory Samsung Android 10, 11, and 12 devices using Routine.
  • Verify installed Routine versions against the fixed version thresholds.
  • Confirm February 2023 or later Samsung security updates are installed where applicable.
  • Prioritize devices used by executives, administrators, or shared-user environments.
  • Document exceptions where vendor updates are unavailable.
Prepared
Confidence
high
Sources
3

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-345: 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-2023-21441 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
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/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
2Source 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
7.4CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N15.8Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2023-21441Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

CWE details

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

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.