Preferred Call modification via unvalidated input
Published Feb 9, 2023 · Updated Mar 24, 2025
Improper input validation in TelephonyUI on Samsung Mobile Devices before SMR Jan-2023 Release 1 allows attackers to configure Preferred Call. Samsung identifies the locus only as unused TelephonyUI code and has not disclosed which input is accepted or how validation fails. Exploitation is local and requires no privileges or user interaction, and the bounded consequence is an unauthorized Preferred Call setting change.
Summary
What happened
Improper input validation in TelephonyUI on Samsung Mobile Devices before SMR Jan-2023 Release 1 allows attackers to configure Preferred Call. Samsung identifies the locus only as unused TelephonyUI code and has not disclosed which input is accepted or how validation fails. Exploitation is local and requires no privileges or user interaction, and the bounded consequence is an unauthorized Preferred Call setting change.
The record
- CVE
- CVE-2023-21428
- Published
- Feb 9, 2023
- Updated
- Mar 24, 2025
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-20
- 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=R(11), S(12), T(13) <SMR Jan-2023 Release 1
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