CVE-2022-21784
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 · uneditedIn WLAN driver, 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: ALPS06704526; Issue ID: ALPS06704462.
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 confidenceOut of bounds write vulnerability in WLAN driver due to missing bounds check, allowing local privilege escalation from System execution privileges. No user interaction required for exploitation.
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= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shellAffected if Version is 11.0 or 12.0 exactly
-
Identify WLAN driver moduleRun 'lsmod | grep -i wlan' or check /sys/module/ for wlan modules in ADB shellAffected if A WLAN driver module is loaded on the device
-
Confirm System privileges contextCheck process privileges by running 'ps -A | grep <wlan_process>' in ADB shell and verify the process is running with System-level privilegesAffected if WLAN driver is running as a System-level process (UID 1000)
Your device is affected if it runs Android 11.0 or 12.0 and has an active WLAN driver module, as the vulnerability exists in the WLAN driver component at these specific Android versions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor patch ALPS06704526 to affected WLAN drivers to remediate the missing bounds check vulnerability.
Latest Android security patch level (monthly security update containing the fix for CVE-2022-21784)
- Check the current Android security patch level on the device: Go to Settings > About Phone > Security Patch Level
- Ensure the device has the latest Android security update installed. For this CVE (CVE-2022-21784), the fix was released through the Android Security Bulletin
- If the device is on Android 11.0 or 12.0, verify that the security patch level is later than the release date of the fix. MediaTek vulnerabilities are typically patched through monthly Android security updates
- Contact the device manufacturer (e.g., Samsung, Xiaomi, Oppo, etc.) or carrier if the security update is not available, to request the patch be applied
- For enterprise or system-level deployment, ensure the device is running the latest firmware provided by the device OEM that includes the MediaTek WLAN driver update with Patch ID ALPS06704526
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21784 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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