LiveActive security incident?Get immediate response
CVE Record

CVE-2023-21145: In updatePictureInPictureMode of ActivityRecord.java, there is a possible bypass of background launch restr...

In updatePictureInPictureMode of ActivityRecord.java, there is a possible bypass of background launch restrictions 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-21145 is an Android flaw where Picture-in-Picture state handling could bypass background launch restrictions. A malicious local app could gain elevated behavior without extra privileges or user interaction. Public sources do not report active exploitation, but affected Android 11 through 13 devices should receive the July 2023 Android security update or equivalent OEM patch.

Executive priority

Treat this as a routine but important mobile fleet patching item. It enables local privilege escalation behavior without user interaction, but public sources here do not show exploitation in the wild. Prioritize enterprise-managed Android 11 through 13 devices that lag behind July 2023 patches.

Technical view

The issue is in Android framework code, specifically updatePictureInPictureMode in ActivityRecord.java. The CVE describes a logic error that may bypass background launch restrictions and lead to local escalation of privilege. Google lists Android 11, 12, 12L, and 13 as affected, with an AOSP framework/base commit referenced from the July 2023 Android security bulletin.

Likely exposure

Exposure is likely limited to Android devices running affected Android 11, 12, 12L, or 13 builds without the relevant July 2023 security bulletin fix or OEM backport.

Exploitation context

The CVE states exploitation is local, needs no additional execution privileges, and needs no user interaction. It is not listed as CISA KEV in the provided bundle, and no cited source confirms active exploitation.

Researcher notes

The source bundle provides limited technical detail beyond the affected method, impact statement, Android versions, bulletin, and AOSP commit. The CWE value appears in the record, but the description points to an Android framework logic error; avoid inferring cryptographic impact from CWE alone.

Mitigation direction

  • Apply the July 2023 Android security update or equivalent OEM patch.
  • Prioritize managed Android 11 through 13 devices in enterprise fleets.
  • Check OEM advisories for device-specific patch availability and timelines.
  • Where patching is delayed, restrict untrusted app installation on managed devices.
  • Monitor Android security bulletins for superseding guidance.

Validation and detection

  • Inventory Android devices by OS version and security patch level.
  • Confirm affected devices show July 2023 security patch level or later.
  • Verify OEM firmware includes the referenced Android framework fix.
  • Review MDM compliance reports for unpatched Android 11 through 13 devices.
  • Track exceptions where vendors have not supplied updated builds.
Prepared
Confidence
medium
Sources
4

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

CWE-326: 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 lookup
cve · low confidence lookup

CVE-2023-21145 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.