LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35674: In onCreate of WindowState.java, there is a possible way to launch a background activity due to a logic err...

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 needed for exploitation.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Android flaw can let a malicious local app gain higher privileges by abusing background activity launch logic. It affects Android 11, 12, 12L, and 13. Because CISA lists it in KEV, treat it as actively exploited and prioritize patching managed mobile devices.

Executive priority

High priority for organizations with Android fleets, especially BYOD or unmanaged app installation risk. Active exploitation evidence means this should be handled as patch compliance work, not deferred as theoretical research.

Technical view

CVE-2023-35674 is a CWE-269 privilege escalation issue in Android WindowState.java onCreate logic. The CVSS 3.1 vector is local, low complexity, low privileges required, no user interaction, scope changed, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to Android devices running versions 11, 12, 12L, or 13 without the relevant September 2023 Android security fixes or later OEM updates.

Exploitation context

CISA KEV confirms known exploitation. The source bundle does not provide exploit details, affected campaigns, or indicators. Exploitation is local, requires existing low privileges, and does not require user interaction.

Researcher notes

The public evidence identifies the vulnerable Android component, impacted versions, CVSS vector, and KEV status. It does not provide safe public detail on exploitation mechanics, indicators, or device-specific OEM patch mapping.

Mitigation direction

  • Apply Android security updates that include the September 2023 bulletin fixes, or later OEM security patches.
  • Prioritize Android 11, 12, 12L, and 13 devices in managed fleets.
  • Check device OEM guidance where patch level availability differs from Google’s bulletin.
  • Restrict installation of untrusted apps until affected devices are updated.
  • Track CISA KEV remediation expectations for regulated or government-facing environments.

Validation and detection

  • Inventory Android OS versions and security patch levels across managed devices.
  • Confirm affected devices have September 2023 Android security fixes or later applicable OEM patches.
  • Review mobile device management compliance reports for stale Android patch levels.
  • Monitor EDR or MTD telemetry for suspicious local privilege escalation behavior.
  • Document exceptions where OEM patches are unavailable and assign compensating controls.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2023-35674 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-35674Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid13, 12L, 12, 11unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.