dbcve.org
AndroidOperating system · Google

CVE-2022-20130

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 transportDec_OutOfBandConfig of tpdec_lib.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-224314979

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

Heap buffer overflow vulnerability in transportDec_OutOfBandConfig function within tpdec_lib.cpp allowing out-of-bounds write. This enables remote code execution without user interaction or elevated privileges, affecting Android-10 through Android-12L media decoding components.

MitigationApply Android security updates/patches for CVE-2022-20130 to the tpdec_lib library in affected Android versions. Prioritize patching given critical CVSS 9.8 rating and network-exploitable RCE capability.

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:= 10.0= 11.0= 12.0= 12.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 'getprop ro.build.version.sdk' to identify the Android OS version
    Affected if Version equals 10.0, 11.0, 12.0, or 12.1 (Android 12L)
  2. Verify SDK version
    Run 'getprop ro.build.version.sdk' to confirm SDK level: 29 (Android 10), 30 (Android 11), 31 (Android 12), 32 (Android 12L)
    Affected if SDK version is 29, 30, 31, or 32
  3. Locate tpdec_lib library
    Search for the library file using 'find /system -name "*tpdec_lib*" 2>/dev/null' or check /system/lib64/ directory for libtpdec_lib.so
    Affected if The tpdec_lib library file exists on the device
  4. Identify media decoding usage
    Check if media applications use the affected transport decoder component by reviewing app permissions or scanning for libtpdec_lib.so loaded in running processes using 'ls -la /proc/*/maps | grep tpdec_lib'
    Affected if Any process has loaded or depends on libtpdec_lib.so for media decoding

Device is affected if running Android 10.0, 11.0, 12.0, or 12.1 (or SDK 29-32) AND the tpdec_lib library is present and actively used for media decoding operations.

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 Android security updates/patches for CVE-2022-20130 to the tpdec_lib library in affected Android versions. Prioritize patching given critical CVSS 9.8 rating and network-exploitable RCE capability.

Recommended fix High confidence

Android 12/12L security patch level 2022-07-01 or later; Android 10/11 should also receive the corresponding monthly security update containing the fix

  1. Check your current Android version by going to Settings > About Phone > Android version
  2. Check your current security patch level by going to Settings > About Phone > Security patch level
  3. Go to Settings > System > System update (or Settings > Software update)
  4. Tap 'Check for updates' or 'Download and install' to get the latest available update
  5. Ensure the security patch level is July 2022 or later (2022-07-01 or newer)
  6. If no update is available, contact your device manufacturer or carrier for the security patch
Caveat None - security patches are backward-compatible; ensure sufficient battery before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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