Security Resilience

CVE-2023-21486

Samsung Android 11.0 … 13.0

Published
04 May 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0025 15th percentile
Risk Priority 39 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-21486 is a medium-severity Improper Export of Android Application Components (CWE-926) vulnerability in Samsung Android. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper export of android application components vulnerability in ImagePreviewActivity in Call Settings to SMR May-2023 Release 1 allows physical attackers to access some media data stored in sandbox.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-21485Same product: Samsung Android
CVE-2025-20934Same product: Samsung Android
CVE-2023-21474Same product: Samsung Android
CVE-2024-34606Same product: Samsung Android
CVE-2023-42527Same product: Samsung Android
CVE-2025-20958Same product: Samsung Android
CVE-2025-20886Same product: Samsung Android
CVE-2023-30683Same product: Samsung Android
CVE-2024-34587Same product: Samsung Android
CVE-2023-42556Same product: Samsung Android

Affected Assets

samsung
android
11.0, 12.0, 13.0

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 partial match
blocks

Defining and enforcing least-privilege access permissions directly prevents unauthorized export of Android components.

PR.PS-06 partial match
blocks

Secure SDLC practices include configuring component exports and permission checks to avoid this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
blocks

A.8.26 only requires that security requirements (including access segregation) be identified and specified during development; it does not itself enforce, implement or configure the restrictions that would stop an improperly-exported Android component from being launched or accessed by unauthorized apps.

blocks

A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust external input, zero-trust verification) and design reviews that can stop unsafe component export decisions, but this is only one slice of the weakness class; many export flaws arise from concrete permission/Intent-filter misconfigurations that the high-level principles and reviews do not themselves enforce.

prevents

Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.

finds

Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.

blocks

Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.

References