dbcve.org
AndroidOperating system · Google

CVE-2022-32630

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 throttling, there is a possible out of bounds write due to an incorrect calculation of buffer size. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07405966; Issue ID: ALPS07405966.

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 buffer size calculation error in the throttling component allows an out-of-bounds write, enabling local privilege escalation to System level. The vulnerability requires System execution privileges to exploit but needs no user interaction.

MitigationApply the MediaTek patch ALPS07405966 to the throttling component. This is a firmware/driver-level fix that should be deployed through standard patch management for affected MediaTek-based systems.

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= 13.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. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The version is 12.0 or 13.0 specifically (not 12L, 12S, or other 13.x variants)
  2. Identify chipset vendor
    Run 'getprop ro.hardware' or check /proc/cpuinfo for MediaTek identifiers
    Affected if The device uses a MediaTek chipset (the vulnerability is in MediaTek's throttling component)
  3. Check throttling component firmware version
    Check /sys/class/thermal/thermal_zone*/* for throttling-related entries, or run 'getprop' for mediaTek throttling properties if available
    Affected if Cannot determine patch level - the patch ALPS07405966 is firmware-level and not visible through standard Android APIs
  4. Verify execution context
    Run 'whoami' or check process privileges via 'ps -A | grep throttling' if a throttling daemon exists
    Affected if Currently running as root or System user (the vulnerability requires System-level execution to exploit)

A device is affected if it runs Android 12.0 or 13.0 on a MediaTek chipset with an unpatched throttling component firmware - the vulnerability cannot be detected through user-accessible means and requires checking against vendor patch bulletins.

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 MediaTek patch ALPS07405966 to the throttling component. This is a firmware/driver-level fix that should be deployed through standard patch management for affected MediaTek-based systems.

Recommended fix Moderate confidence

Android Security Patch Level May 2023 or later containing MediaTek patch ALPS07405966

  1. Check the Android Security Patch Level on the device under Settings > About Phone > Android version or Security Patch Level
  2. Verify the device has the May 2023 Android Security Update or later (which includes MediaTek patch ALPS07405966)
  3. If the device does not have the required security update, check for a system software update from the device manufacturer
  4. If no update is available from the OEM, contact the device vendor or MediaTek directly for the patch
  5. Alternatively, if this is a MediaTek-based device, verify with the OEM that ALPS07405966 has been applied

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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