CVE-2022-20019
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 libMtkOmxGsmDec, there is a possible information disclosure due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05917620; Issue ID: ALPS05917620.
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 confidenceAn incorrect bounds check in libMtkOmxGsmDec (MediaTek's GSM audio decoder) allows reading beyond allocated buffer boundaries, leading to local information disclosure. No user interaction or elevated privileges are 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= 10.0= 11.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Version is 10.0 or 11.0 exactly (not 10.x or 11.x)
-
Verify MediaTek SoC presenceRun 'getprop ro.mediatek.platform' - this should return a MediaTek platform identifier if the device uses MediaTek hardwareAffected if Property returns a value containing 'MT' (e.g., MT6785, MT6885) indicating MediaTek chipset
-
Locate the vulnerable libraryRun 'find /system -name "libMtkOmxGsmDec*" 2>/dev/null' to search for the GSM decoder library in system partitionsAffected if File matching 'libMtkOmxGsmDec' is found in /system/lib or /vendor/lib directory
-
Check if library is loaded in running processesRun 'cat /proc/*/maps 2>/dev/null | grep -i libMtkOmxGsmDec' or use 'ls -la /sys/module | grep -i gsm' to see if the module is loadedAffected if The library appears in any process memory maps, indicating it is actively loaded and potentially in use
Device is affected if it runs Android 10.0 or 11.0, uses a MediaTek SoC, and contains the libMtkOmxGsmDec library which is loaded by any process on the system.
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 ALPS05917620 through MediaTek firmware or device-specific updates; if patch unavailable, consider disabling the affected GSM decoder component or restricting access to the vulnerable library.
Apply the vendor-supplied patch ALPS05917620 via Android security update (check with device OEM for availability)
- 1. Contact your device manufacturer (OEM) to request the security update containing MediaTek patch ALPS05917620
- 2. Verify that the patch has been applied by checking the Android security patch level in Settings > About Phone > Security Patch Level
- 3. Alternatively, apply the latest Android security update for Android 10.0 or 11.0 as released by your device manufacturer, which should include this fix
- 4. If your device is no longer receiving updates from the manufacturer, consider upgrading to a device with ongoing security support
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-20019 — 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-20019 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