dbcve.org
AndroidOperating system · Google

CVE-2022-20087

MEDIUM · 6.7 CVSS v3.1 Published 2022-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06477970; Issue ID: ALPS06477970.

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

In ccu, an unspecified component in MediaTek/ALPS Android systems, a missing bounds check allows an out-of-bounds write, which can be exploited for local privilege escalation from System privileges.

MitigationApply the vendor patch ALPS06477970 to the affected system component; without patch availability, restrict local access to trusted users and monitor for exploitation indicators.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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. Identify Android version
    Check system settings or run 'getprop ro.build.version.release' to determine the installed Android OS version
    Affected if The version is exactly 11.0 or 12.0 (note: other versions or custom ROMs have different exposure)
  2. Confirm MediaTek chipset
    Run 'getprop ro.chipname' or 'cat /proc/cpuinfo' to identify the SoC manufacturer; the ccu component is specific to MediaTek platforms
    Affected if The device uses a MediaTek chipset (devices with Qualcomm, Exynos, or other SoCs are not affected by this MediaTek-specific flaw)
  3. Verify ccu component presence
    Check for the ccu daemon or service in /system/bin or /vendor/bin; run 'ls -la /system/bin/ccu*' or search via 'find /system -name *ccu*'
    Affected if The ccu component exists in the system image (the vulnerability only applies if this component is present and enabled)
  4. Check patch installation status
    Query the system build properties or security patch level via 'getprop ro.build.version.security_patch'; consult vendor documentation for patch ALPS06477970 inclusion
    Affected if The security patch level predates the vendor fix or the specific patch ALPS06477970 is not listed as applied

The environment is affected if the device runs Android 11.0 or 12.0 on a MediaTek chipset with the ccu component present and the ALPS06477970 patch has not been applied.

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 the vendor patch ALPS06477970 to the affected system component; without patch availability, restrict local access to trusted users and monitor for exploitation indicators.

Recommended fix Moderate confidence

Android 13 with latest security patches (includes fix for CVE-2022-20087)

  1. Identify if the device uses a MediaTek chipset (check device specifications or settings)
  2. Verify the device is running Android 11.0 or 12.0
  3. Contact the device manufacturer (OEM) to confirm if ALPS06477970 patch has been released for your specific device model
  4. Apply the latest Android Security Patch Level available from your device manufacturer - this patch was addressed in MediaTek security updates
  5. If the manufacturer has not released the patch, consider applying any available OEM-specific security updates that include this MediaTek fix
Caveat Some devices running Android 11/12 may not receive this specific MediaTek patch update from their OEM; upgrading to Android 13 may be manufacturer-dependent

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20087 — 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-20087 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