BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-20144High confidence

This could lead to local escalation of privilege with no additional execution privileges needed

Unknown · Android

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 3 Aug 2024

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Android and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-25404

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

In multiple functions of AvatarPhotoController.java, there is a possible access to content owned by system content providers 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-10 Android-11Android ID: A-250637906

What

In multiple functions of AvatarPhotoController.java, there is a possible access to content owned by system content providers 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-10 Android-11Android ID: A-250637906

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In multiple functions of AvatarPhotoController.java, there is a possible access to content owned by system content providers 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-10 Android-11Android ID: A-250637906

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2022-2234Android Patchday Dezember 2022

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen und vertrauliche Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2022-0137Android Patchday Juni 2022

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um seine Privilegien zu erhöhen, vertrauliche Informationen offenzulegen, beliebigen Code auszuführen und einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220622Security Bulletin 22 Jun 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jun 2022, published on 22 June 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-524Multiples vulnérabilités dans Google Android

d?id=CVE-2022-20134 Référence CVE CVE-2022-20135 https://www.cve.org/CVERecord?id=CVE-2022-20135 Référence CVE CVE-2022-20136 https://www.cve.org/CVERecord?id=CVE-2022-20136 Référence CVE CVE-2022-20137 https://www.cve.org/CVERecord?id=CVE-2022-20137 Référence CVE CVE-2022-20138 https://www.cve.org/CVERecord?id=CVE-2022-20138 Référence CVE CVE-2022-20140 https://www.cve.org/CVERecord?id=CVE-2022-20140 Référence CVE CVE-2022-20141 https://www.cve.org/CVERecord?id=CVE-2022-20141 Référence CVE CVE-2022-20142 https://www.cve.org/CVERecord?id=CVE-2022-20142 Référence CVE CVE-2022-20143 https://www.cve.org/CVERecord?id=CVE-2022-20143 Référence CVE CVE-2022-20144 https://www.cve.org/CVERecord?id=CVE-2022-20144 Référence CVE CVE-2022-20145 https://www.cve.org/CVERecord?id=CVE-2022-20145 Référence CVE CVE-2022-20147 https://www.cve.org/CVERecord?id=CVE-2022-20147 Référence CVE CVE-2022-20210 https://www.cve.org/CVERecord?id=CVE-2022-20210 Référence CVE CVE-2022-21745 https://www.cve.org/CVERecord?id=CVE-2022-21745 Référence CVE CVE-2022-22082 https://www.cve.org/CVERecord?id=CVE-2022-22082 Référence CVE CVE-2022-22083 https://www.cve.org/CVERecord?id=CVE-2022-22083 Référence CVE CVE-2022-22084 https://www.cve.org/CVERecord?id=CVE-2022-22084 Référence CVE CVE-2022-22085 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-1084Multiples vulnérabilités dans Google Android

s données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Android du 05 décembre 2022 https://source.android.com/docs/security/bulletin/2022-12-01 Référence CVE CVE-2021-0934 https://www.cve.org/CVERecord?id=CVE-2021-0934 Référence CVE CVE-2021-39617 https://www.cve.org/CVERecord?id=CVE-2021-39617 Référence CVE CVE-2021-39660 https://www.cve.org/CVERecord?id=CVE-2021-39660 Référence CVE CVE-2021-39795 https://www.cve.org/CVERecord?id=CVE-2021-39795 Référence CVE CVE-2022-20124 https://www.cve.org/CVERecord?id=CVE-2022-20124 Référence CVE CVE-2022-20144 https://www.cve.org/CVERecord?id=CVE-2022-20144 Référence CVE CVE-2022-20240 https://www.cve.org/CVERecord?id=CVE-2022-20240 Référence CVE CVE-2022-20411 https://www.cve.org/CVERecord?id=CVE-2022-20411 Référence CVE CVE-2022-20442 https://www.cve.org/CVERecord?id=CVE-2022-20442 Référence CVE CVE-2022-20444 https://www.cve.org/CVERecord?id=CVE-2022-20444 Référence CVE CVE-2022-20449 https://www.cve.org/CVERecord?id=CVE-2022-20449 Référence CVE CVE-2022-20466 https://www.cve.org/CVERecord?id=CVE-2022-20466 Référence CVE CVE-2022-20468 https://www.cve.org/CVERecord?id=CVE-2022-20468 Référence CVE CVE-2022-20469 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-011953Google の Android における脆弱性

Google の Android には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Android: Android-10 Android-11
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Jun 2022 · Last source change 3 Aug 2024, 02:02 UTC · CWE not yet assigned

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-25404
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification, affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-20144 · cve.blacktree.nl