CVE-2023-35674
LPE in Google Android 11.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). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-35674 is a high-severity Improper Privilege Management (CWE-269) vulnerability in Google Android. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 14% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-35674 is a logic error in the onCreate method of WindowState.java within the Android frameworks/base component. The flaw permits an application to launch a background activity, which can be leveraged for unauthorized actions on the device. It carries a CVSS 3.1 score of 7.8 and is tracked under CWE-269.
A local attacker with existing low-privileged access can exploit the issue without user interaction or additional execution rights, resulting in full escalation that affects confidentiality, integrity, and availability at a high level. The vulnerability resides in core window-management handling, allowing the malicious activity to bypass intended restrictions on background launches.
The September 2023 Android security bulletin addresses the issue through patches referenced in the public commit 7428962d3b064ce1122809d87af65099d1129c9e, and the flaw appears in CISA's known exploited vulnerabilities catalog. The current EPSS score remains low at 0.0012 with no indicated upward trajectory.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-39674
Vulnerability Data
In onCreate of WindowState.java, there is a possible way to launch a background activity due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…
more
needed for exploitation.
- CWE(s)
- KEV Date Added
- 13 September 2023
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Policy addresses roles, responsibilities, and privilege management to prevent improper privilege assignments.
Access supervision ensures privileges are assigned and managed without improper escalation or retention.
Assigning group/role memberships and access authorizations (privileges) while reviewing accounts addresses improper privilege management.
Enforces proper privilege management by requiring all decisions through the verified reference monitor.
By mandating division of duties across roles, the control enforces proper privilege management and prevents a single entity from controlling an entire sensitive process.
Implements core proper privilege management by restricting to only required rights.
Policy requires training on privilege management and least privilege, making it harder to exploit improper privilege management weaknesses.
Training covers proper privilege management practices, making incorrect privilege assignments less likely.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).
A.8.3's access restriction mechanisms (per-identity rights, dynamic access management, isolation) block exploitation of improperly assigned privileges when the mis-assignment sits in a layer A.8.3's own authorization decisions override, but many CWE-269 instances are the access control itself being wrong (role definitions, self-grant, setuid programs, privilege-not-reset), where A.8.3 IS the defective layer and cannot block its own failure.
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.