Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-21462 is a medium-severity Insertion of Sensitive Information Into Debugging Code (CWE-215) vulnerability in Samsung Quick Share. Its CVSS base score is 4.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 4th 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
- 🇪🇺 ENISA EUVD: EUVD-2023-25630
Vulnerability Data
The sensitive information exposure vulnerability in Quick Share Agent prior to versions 3.5.14.18 in Android 12 and 3.5.16.20 in Android 13 allows to local attacker to access MAC address without related permission.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.4.2
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.
Explicitly calls for removing confidential data from processes, logs, and memory dumps that debug code commonly exposes.
Hardened configuration baselines and deployment checks can ensure debug features and associated data are disabled in production.
Secure SDLC practices directly prevent developers from embedding sensitive information inside debugging statements or code paths.
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.
Secure SDLC mandates removal of debug code and sensitive data before release.
Secure coding standards explicitly prohibit embedding secrets or debug statements.
Security testing in development catches debug statements and sensitive data leaks.
A.8.31 separates environments and restricts what reaches production; it does not stop sensitive information from being inserted into debugging code in the first place, so the weakness can still be present and exploitable if debugging code slips into production.