CVE-2022-20014
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 vow driver, there is a possible memory corruption due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05857308; Issue ID: ALPS05857308.
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 confidenceA memory corruption vulnerability exists in the vow driver (likely an audio/voice driver) due to improper input validation. The flaw allows a local attacker to escalate privileges to System level without requiring user interaction. The vulnerability stems from insufficient validation of input data passed to the driver, leading to memory corruption that can be exploited for privilege escalation.
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= 10.0= 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' via adb shell)Affected if The installed version is 10.0, 11.0, or 12.0
-
Verify vow driver presenceCheck if the vow driver module exists on the device by looking for vow-related files in /system/lib/modules/ or /vendor/lib/modules/ (or run 'ls -la /system/lib/modules/*vow*' via adb shell)Affected if A vow driver module is present on the device
-
Confirm driver is loadedCheck if the vow driver is actively loaded by running 'lsmod | grep vow' or checking /proc/modules via adb shellAffected if The vow driver module is currently loaded in memory
A device is affected if it runs Android 10.0, 11.0, or 12.0 and has the vow driver module present and loaded, as the privilege escalation vulnerability requires this specific driver to be exploitable.
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 the vendor patch (ALPS05857308) to address the input validation vulnerability in the vow driver. Since this is a local privilege escalation requiring System-level access initially, prioritize patching systems where untrusted local users have access.
Android Security Patch Level 2022-05-01 or later (contact OEM for device-specific firmware)
- Check the current Android security patch level on the affected device (Settings > Security > Security patch level)
- Contact the device manufacturer (OEM) for the specific firmware update containing the MediaTek VOW driver fix
- Request the ALPS05857308 patch or security update that addresses CVE-2022-20014
- Apply the OEM-provided system update that includes the May 2022 Android security patch or later
- Verify the vulnerability is resolved by confirming the patch level and potentially using a vulnerability scanner
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20014 — 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-20014 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