LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0608: In handleAppLaunch of AppLaunchActivity.java, there is a possible arbitrary activity launch due to a confus...

In handleAppLaunch of AppLaunchActivity.java, there is a possible arbitrary activity launch due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-174870704

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-0608 is an Android local privilege-escalation issue. A vulnerable Android component could be misused to launch an arbitrary activity, potentially giving a local app more access without extra permissions or user interaction. The provided sources do not include CVSS scoring, a CWE, or a detailed affected-device matrix.

Executive priority

Treat this as a patch-verification item for Android fleets, not as an emergency based on the supplied evidence. Priority rises for devices lacking vendor security updates or running unsupported Android builds.

Technical view

The flaw is described in handleAppLaunch of AppLaunchActivity.java as an arbitrary activity launch caused by a confused deputy. The stated impact is local escalation of privilege with no additional execution privileges needed and no user interaction. The source bundle lists Android with version scope “Android kernel,” but does not provide exploit mechanics or fixed build identifiers.

Likely exposure

Exposure is limited to Android environments matching the vendor bulletin and CVE record. The provided affected entry names Android and “Android kernel,” but does not identify specific Pixel models, Android patch levels, or downstream OEM status.

Exploitation context

The source bundle does not show active exploitation, public exploit availability, or KEV listing. The issue requires local context but not user interaction or additional execution privileges, making unmanaged or unpatched Android devices the main concern.

Researcher notes

Evidence is sparse: no CVSS, CWE, fixed commits, affected model list, or exploit details are present in the source bundle. Analysis should stay anchored to the Android/Pixel bulletin and CVE wording until vendor-specific advisories confirm scope.

Mitigation direction

  • Review the June 2021 Pixel security bulletin for vendor guidance.
  • Apply applicable Android or Pixel security updates from the device vendor.
  • Confirm downstream OEM firmware includes the relevant June 2021 security fixes.
  • Prioritize managed devices that cannot receive current Android security patches.

Validation and detection

  • Inventory Android devices and recorded security patch levels.
  • Check whether devices received the June 2021 Android or Pixel security bulletin fixes.
  • Validate OEM advisories for non-Pixel Android devices before assuming coverage.
  • Review mobile EDR or MDM telemetry for unusual local privilege escalation indicators.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2021-0608 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
2Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid kernelListed
Weakness

CWE details

No CWE listed

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