dbcve.org
AndroidOperating system · Google

CVE-2022-20610

HIGH · 8.8 CVSS v3.1 Published 2022-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 cellular modem firmware, there is a possible out of bounds read due to a missing bounds check. This could lead to remote code execution with LTE authentication needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-240462530References: N/A

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

A missing bounds check in cellular modem firmware allows an out-of-bounds read vulnerability that could be exploited for remote code execution. The attack requires LTE authentication, meaning an attacker would need access to the LTE network (e.g., a malicious base station or compromised network element). This is a memory safety flaw in the baseband/modem processor, separate from the main application processor.

MitigationApply modem firmware updates provided by the device OEM and/or cellular chipset vendor (Qualcomm, MediaTek, etc.) through carrier channels. Until the update is available, consider restricting device use on untrusted LTE networks or implementing network-level monitoring for anomalous modem behavior.

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:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm device has cellular modem capability
    Identify if the Android device contains a cellular modem (LTE/4G/5G) by checking device specifications or settings under Settings > About Phone > SIM Status or Network settings. Devices without cellular modems (e.g., WiFi-only tablets) are not affected.
    Affected if Device has an active cellular modem and connects to LTE networks
  2. Check modem/baseband firmware version
    Access the baseband/modem firmware version through Android settings (Settings > About Phone > Baseband Version or Settings > Connections > Mobile Networks > Network Mode). This version is specific to the cellular chipset vendor (Qualcomm, MediaTek, etc.) and is separate from the Android OS version.
    Affected if Unable to determine or confirm the baseband version due to OEM restrictions, indicating potential unpatched firmware
  3. Verify LTE network exposure
    Determine if the device connects to LTE networks. The vulnerability requires an attacker with LTE network access (malicious base station or compromised network element). Check if the device uses LTE/4G for voice or data connectivity.
    Affected if Device actively connects to LTE networks without network-level filtering or trusted carrier controls

A user is affected if their Android device with a cellular modem connects to LTE networks and the modem firmware has not been updated by the OEM/chipset vendor to address the missing bounds check vulnerability.

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 modem firmware updates provided by the device OEM and/or cellular chipset vendor (Qualcomm, MediaTek, etc.) through carrier channels. Until the update is available, consider restricting device use on untrusted LTE networks or implementing network-level monitoring for anomalous modem behavior.

Recommended fix Moderate confidence

Android Security Bulletin (device-specific firmware update containing patch for Android ID A-240462530)

  1. Check your Android device for the latest system updates and install them. Go to Settings > System > Software Update (or Settings > About Phone > Software Update)
  2. Ensure your device has the latest Android Security Patch Level. Go to Settings > Security > Security patch level to verify
  3. If your device manufacturer has released a firmware update for the cellular modem (often included in monthly security updates), install it
  4. For enterprise or high-risk users, consider using devices from manufacturers that provide timely modem firmware updates
  5. Note: This vulnerability is in cellular modem firmware, not the Android OS kernel itself. The fix is delivered through carrier/manufacturer firmware updates bundled with Android security bulletins
Caveat Modem firmware updates carry minimal risk but may cause temporary loss of service if interrupted. Ensure device is charged and connected to stable power before updating.

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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