dbcve.org
AndroidOperating system · Google

CVE-2022-32629

MEDIUM · 6.7 CVSS v3.1 Published 2022-12-05
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 isp, 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: ALPS07310774; Issue ID: ALPS07310774.

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 missing bounds check in the ISP (Image Signal Processor) component allows an out-of-bounds write, potentially enabling local privilege escalation from System execution privileges. The vulnerability stems from insufficient input validation in the ISP processing pipeline.

MitigationApply vendor patch ALPS07310774 to address the missing bounds check in the ISP component. This is a MediaTek-specific patch for their ISP implementation.

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:= 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. Verify Android version is 12.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version equals 12.0 exactly
  2. Confirm MediaTek chipset is in use
    Run 'getprop ro.hardware' or 'cat /proc/cpuinfo' via ADB to identify the SoC vendor
    Affected if Device uses a MediaTek chipset (hardware identifier contains 'mtk' or 'mediatek')
  3. Check ISP component version
    Inspect MediaTek ISP driver version via 'cat /sys/class/video4linux/video*/name' or check vendor-specific ISP modules with 'lsmod | grep isp' via ADB
    Affected if ISP driver module is loaded and version cannot be verified against vendor patch ALPS07310774
  4. Verify current privilege level
    Run 'id' or 'whoami' via ADB shell to confirm execution context
    Affected if Running with System-level privileges (not root, but elevated system access)
  5. Check vendor security patch level
    Run 'getprop ro.build.version.security_patch' via ADB to see installed security updates
    Affected if Security patch level is earlier than the July 2022 Android security bulletin

Device is affected if running Android 12.0 on a MediaTek chipset with ISP component not patched with ALPS07310774 and the July 2022 security update not 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 vendor patch ALPS07310774 to address the missing bounds check in the ISP component. This is a MediaTek-specific patch for their ISP implementation.

Recommended fix Moderate confidence

Android 12.0 with September 2022 Security Patch Level (or later) that incorporates MediaTek patch ALPS07310774

  1. Check if your device has the September 2022 Android Security Patch Level or later installed, as MediaTek patches are delivered through Android's monthly security bulletins
  2. Go to Settings > About Phone > Software Information on the affected Android 12.0 device
  3. Verify the Security Patch Level under Android security bulletin listings (corp.mediatek.com reference ALPS07310774)
  4. If the device does not have the patch, check for a system update from your device manufacturer
  5. Apply any available system updates that include the September 2022 Android Security Bulletin or subsequent updates
  6. If no update is available from your device manufacturer, consider whether the device manufacturer has released a specific firmware update addressing this MediaTek ISP vulnerability
  7. For enterprise or managed devices, apply the update through your mobile device management (MDM) system after testing
Caveat Security patches are generally backward-compatible; this is a bug fix and should not introduce breaking changes to functionality

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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