CVE-2023-20915
Google Android 10.0 … 13.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-20915 is a high-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Google Android. Its CVSS base score is 7.8 (High).
Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25083
Vulnerability Data
In addOrReplacePhoneAccount of PhoneAccountRegistrar.java, there is a possible way to enable a phone account without user interaction due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User…
more
interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-246930197
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
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.
A.8.25 mandates an SDLC process that includes security requirements, checkpoints, secure coding guidelines, testing and developer training, which reaches a slice of control-flow defects but leaves most implementation bugs untouched without perfect enforcement at every checkpoint.
Secure coding standards and reviews directly target flawed control-flow implementations.
Security testing in development and acceptance can detect paths that deviate from intended logic.
A.8.32 mandates a formal process for planning, authorizing, testing and documenting changes but does not itself inspect, correct or block the incorrect control-flow logic that CWE-670 describes; the defect can still be introduced and exploited if the developer writes it and the process accepts it.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-670, a class-level weakness, and none of its children carries one either.