CVE-2022-20419: Launcher puts IApplicationThread inside ActivityOptions and it may be sent to launched app

platform/frameworks/base Updated 02 Oct 2025

Summary

01/10/2022
Yes i
Critical
Not published

CVE-2022-20419: In setOptions of ActivityRecord.java, there is a possible load any arbitrary Java code into launcher process due to a logic error in the code. Affects platform/frameworks/base across 2 version ranges.

>= 12L:0, < 12L:2022-10-01 >= 13:0, < 13:2022-10-01

Fixed in 12L:2022-10-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package under scrutiny is platform/frameworks/base in the Android ecosystem. This package is responsible for providing the fundamental building blocks and essential functionalities for the Android operating system. It includes various components such as activities, services, content providers, and broadcast receivers. The vulnerability affects versions 12L and 13 of the package. The package is susceptible to a logic error in the code that allows the launcher to load arbitrary Java code into its process. This vulnerability can lead to a local escalation of privilege without requiring additional execution privileges. Exploitation of this vulnerability does not require user interaction.

Vulnerability Detail

The vulnerability arises in the setOptions function of the ActivityRecord.java file. Due to a logic error, the launcher process can load any arbitrary Java code. This code can be sent to the launched app, resulting in a local escalation of privilege. The impact of this vulnerability is critical as it allows an attacker to execute arbitrary code within the launcher process, potentially gaining unauthorized access to sensitive information or performing malicious actions. The vulnerability was introduced in version 12L and has been fixed in version 13, with the fix being released on October 1, 2022.

How To Fix

Minimum fixed version

12L:2022-10-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

In conclusion, the platform/frameworks/base package in the Android ecosystem is vulnerable to a logic error that allows the launcher to load arbitrary Java code into its process. This can result in a local escalation of privilege. It is crucial to update to version 13 or later of the package to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for platform/frameworks/base →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary Java code within the launcher process, potentially leading to a local escalation of privilege.

No, user interaction is not needed for exploitation of this vulnerability.

Versions 12L and 13 of the platform/frameworks/base package are affected.

Yes, the vulnerability has been fixed in version 13 of the package, with the fix released on October 1, 2022.

More information about this vulnerability can be found in the Open Source Vulnerability database: [https://storage.googleapis.com/android-osv/ASB-A-237290578.json].

Related vulnerabilities

Recent vulnerabilities recorded for platform/frameworks/base.

How To Fix

Minimum fixed version

12L:2022-10-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback