Security readout for executives and security teams
Plain-English summary
This is a Samsung mobile-device issue in the phone interface component. A local attacker could change Preferred Call behavior. The published impact is limited to low availability impact, with no reported confidentiality or integrity impact.
Executive priority
Treat this as routine mobile fleet hygiene, not an emergency. The business priority is ensuring old Samsung devices are not left behind on pre-January 2023 security updates.
Technical view
TelephonyUI before SMR Jan-2023 Release 1 on Samsung Mobile Devices running R(11), S(12), or T(13) has CWE-20 improper input validation. CVSS 3.1 is 4.0: local attack vector, low complexity, no privileges or user interaction, unchanged scope, and low availability impact only.
Likely exposure
Exposure is limited to Samsung Mobile Devices on Android 11, 12, or 13 that had not received Samsung's January 2023 SMR Release 1 or later security update.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates local access is required, so this is more relevant to unmanaged or physically exposed devices than remote internet exposure.
Researcher notes
The root cause is CWE-20 improper input validation in TelephonyUI. Samsung states the patch removes unused code. Public sources do not provide detailed attack mechanics, indicators, or a workaround beyond applying vendor updates.
Mitigation direction
- Apply Samsung SMR Jan-2023 Release 1 or later.
- Prioritize managed Samsung Android fleets still below the January 2023 security patch level.
- Check Samsung guidance for any device-specific update availability.
- Track remediation through MDM compliance policies and exception reporting.
Validation and detection
- Inventory Samsung devices running Android 11, 12, or 13.
- Confirm each device reports January 2023 SMR Release 1 or newer.
- Review MDM records for devices below the required security patch level.
- Validate that unsupported devices have compensating controls or replacement plans.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-20: 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 lookupCVE-2023-21428 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L2.51.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://security.samsungmobile.com/securityUpdate.smsb?year=2023&month=01CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.