Protected-file disclosure through undisclosed unused code
Published Feb 9, 2023 · Updated Mar 24, 2025
Insufficient data-authenticity verification in Samsung Routines on Android 10 through 12 allows local users to read protected files. Samsung identifies the vulnerable locus only as unused code and has not disclosed what data is accepted or how that code reaches protected files. Exploitation requires local access, and the published impact is limited to protected-file access.
Summary
What happened
Insufficient data-authenticity verification in Samsung Routines on Android 10 through 12 allows local users to read protected files. Samsung identifies the vulnerable locus only as unused code and has not disclosed what data is accepted or how that code reaches protected files. Exploitation requires local access, and the published impact is limited to protected-file access.
The record
- CVE
- CVE-2023-21441
- Published
- Feb 9, 2023
- Updated
- Mar 24, 2025
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Routines
- Classifications
- CWE-345, T1409
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2023CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <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)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo