dbcve.org
AndroidOperating system · Google

CVE-2022-32641

MEDIUM · 6.7 CVSS v3.1 Published 2023-01-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 meta wifi, there is a possible out of bounds read 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: ALPS07453594; Issue ID: ALPS07453594.

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 · high confidence

In meta wifi (MediaTek's Android WiFi framework), an out-of-bounds read vulnerability exists due to a missing bounds check in the WiFi subsystem. This allows a local attacker with System-level privileges to escalate privileges without user interaction.

MitigationApply vendor patch ALPS07453594 through system/firmware update; this is a vendor-specific WiFi component requiring OTA or system update deployment.

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= 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 OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 11.0, 12.0, or 13.0 exactly (not a later security patch)
  2. Verify MediaTek WiFi component is present
    Check for MediaTek WiFi driver by running 'getprop | grep mtk' or inspect /system/lib/modules for MediaTek WiFi kernel modules
    Affected if Device uses MediaTek WiFi chipset and the meta wifi component is loaded
  3. Confirm System-level access context
    Determine if the device has been compromised to System-level or if you are analyzing a device where attacker already has System privileges
    Affected if Attacker already has System-level privileges on the device (required for exploitation)
  4. Check firmware/build date
    Run 'getprop ro.build.date' or check Settings > About Phone > Build number for patch level
    Affected if Build predates the ALPS07453594 vendor patch (no OTA/firmware update applied)

Device is affected if running Android 11.0, 12.0, or 13.0 with a MediaTek WiFi component and has not received the vendor-specific patch ALPS07453594 through an OTA or system update.

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 ALPS07453594 through system/firmware update; this is a vendor-specific WiFi component requiring OTA or system update deployment.

Recommended fix Moderate confidence

Android 13.0 with September 2022 security patch level or later; or Android 14/15 which include this fix in later monthly security updates

  1. 1. Check the device's current Android security patch level in Settings > About Phone > Security Patch Level
  2. 2. Verify if the device has received the Android security bulletin patch for September 2022 or later (CVE-2022-32641 was addressed in MediaTek's September 2022 security update)
  3. 3. If the device is from a carrier or OEM, check for available system updates that include the September 2022 security patch or later
  4. 4. Apply any available system updates to receive the patch for ALPS07453594
  5. 5. After updating, confirm the security patch level reflects the patched version

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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