dbcve.org
AndroidOperating system · Google

CVE-2022-20052

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In mdp, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS05836642; Issue ID: ALPS05836642.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A use-after-free vulnerability exists in the mdp (media display processor) component that allows local privilege escalation to System execution level. The vulnerability requires user interaction to trigger and involves memory corruption where freed memory is accessed after being deallocated. This is a memory safety issue in the display processing subsystem of the affected system.

MitigationApply vendor patch ALPS05836642 to address the use-after-free vulnerability in the mdp component. As this appears to be firmware-level, contact the device/vendor for the appropriate patch and ensure system privileges are not granted to untrusted applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 11.0= 12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is exactly 11.0 or 12.0 (note: only these specific versions are affected, not ranges)
  2. Verify vendor security patch level
    Check Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if Security patch level is earlier than the date when ALPS05836642 was released (contact device vendor for specific patch date)
  3. Confirm mdp component exposure
    This vulnerability exists in the mdp (media display processor) firmware component. On affected Android devices, this component handles display processing. There is no direct user-accessible method to check mdp version; this requires vendor-level diagnostics.
    Affected if Device runs Android 11.0 or 12.0 and the vendor has not applied the ALPS05836642 patch to the firmware

A user is affected if their device runs Android 11.0 or 12.0 and the vendor patch ALPS05836642 has not been applied to address the use-after-free in the mdp display processor component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch ALPS05836642 to address the use-after-free vulnerability in the mdp component. As this appears to be firmware-level, contact the device/vendor for the appropriate patch and ensure system privileges are not granted to untrusted applications.

Recommended fix High confidence
  1. Identify if your device uses a MediaTek chipset (check device specifications)
  2. Contact your device manufacturer (OEM) to confirm they have incorporated MediaTek patch ALPS05836642 to address this use-after-free vulnerability in the mdp component
  3. Check that your device has the latest Android security update installed (go to Settings > Security > Security patch level)
  4. If the patch is not available, monitor your device manufacturer's support channels for the forthcoming OTA update containing this fix
  5. Apply any available system updates promptly after verifying they come from your legitimate device manufacturer

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20052 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data