CVE-2022-20389VulnerabilityPublished 13 Sep 2022Updated 5 Jun 2025

CVE-2022-20389: Android · Elevation of privilege

Affects AndroidSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Mitigation should focus on a multi-layered approach: 1) Immediate identification of affected devices within the organization, focusing on Android SoC versions known to be vulnerable. 2) Applying official security patches and firmware updates from device manufacturers and SoC vendors as soon as they become available. Since patch links are not provided, organizations should monitor vendor advisories closely. 3) Implement network-level protections such as restricting unnecessary inbound connections to mobile devices, using VPNs, and deploying mobile threat defense solutions that can detect anomalous behavior indicative of exploitation attempts. 4) Enforce strict device management policies using Mobile Device Management (MDM) platforms to control app installations and permissions, reducing the attack surface. 5) Educate users about the risks of connecting to untrusted networks and encourage regular device updates. 6) For high-risk environments, consider isolating Android devices or limiting their access to sensitive systems until patches are applied. 7) Conduct regular security assessments and penetration testing focused on mobile device security to detect potential exploitation.

Description

Summary:Product: AndroidVersions: Android SoCAndroid ID: A-238257004

Impact

For European organizations, the impact of CVE-2022-20389 could be significant, especially for those relying on Android devices for business operations, communications, and data access. The ability for an attacker to remotely elevate privileges without user interaction poses a high risk of data breaches, espionage, and disruption of services. Organizations handling sensitive personal data under GDPR could face compliance risks if devices are compromised. The vulnerability could also be exploited to deploy malware or ransomware, leading to operational downtime and financial losses. Given the widespread use of Android devices across European enterprises and public sector entities, the threat extends to mobile workforce security and critical infrastructure management. Additionally, sectors such as finance, healthcare, and government, which often use Android devices for secure communications and applications, are at increased risk. The potential for device takeover could also facilitate lateral movement within corporate networks, amplifying the threat.

Summary

CVE-2022-20389 is a critical elevation of privilege vulnerability affecting Android SoC (System on Chip) components. The vulnerability allows an unauthenticated attacker to gain elevated privileges on the affected Android device without requiring any user interaction. With a CVSS 3.1 base score of 9.8, this vulnerability is highly severe, impacting confidentiality, integrity, and availability. The attack vector is network-based (AV:N), meaning exploitation can occur remotely without physical access. The vulnerability requires no privileges (PR:N) and no user interaction (UI:N), making it easier to exploit. Successful exploitation could allow an attacker to execute arbitrary code with elevated privileges, potentially leading to full device compromise, unauthorized access to sensitive data, and disruption of device functionality. The vulnerability affects Android SoC versions, which are integral to the functioning of Android devices, including smartphones and tablets. Although no known exploits have been reported in the wild as of the publication date, the critical nature of this vulnerability demands immediate attention. The lack of patch links suggests that remediation may require updates from device manufacturers or SoC vendors. This vulnerability underscores the importance of securing the hardware-software interface in mobile devices, as SoC-level flaws can undermine the entire device security model.

References

source.android.com/security/bulletin/2022-09-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 7 Jul 2025, 18:41 UTC

Technical details

References

Community reviews

Related threats