CVE-2022-20210
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 · uneditedThe UE and the EMM communicate with each other using NAS messages. When a new NAS message arrives from the EMM, the modem parses it and fills in internal objects based on the received data. A bug in the parsing code could be used by an attacker to remotely crash the modem, which could lead to DoS or RCE.Product: AndroidVersions: Android SoCAndroid ID: A-228868888
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 confidenceA parsing vulnerability exists in the modem's NAS (Non-Access Stratum) message handling code. When processing incoming NAS messages from the EMM (EPS Mobility Management), the modem fills internal objects based on received data. A bug in this parsing logic can be exploited by a remote attacker to crash the modem, potentially achieving denial of service or remote code execution.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device's baseband/modem firmware versionGo to Settings > About Phone > SIM Status, or dial *#*#4636#*#* to access testing info, or run 'getprop | grep baseband' via ADB shellAffected if The baseband version cannot be determined or is an unpatched release from the device manufacturer/carrier
-
Determine the device's Android version and security patch levelGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.security_patch' via ADBAffected if The device is running any Android version (as all versions are listed as affected) and lacks the vendor-specific modem firmware update
-
Identify the device manufacturer and carrierCheck Settings > About Phone for manufacturer and model information, and identify your mobile carrierAffected if The manufacturer or carrier has not released a modem firmware update addressing this NAS parsing vulnerability
-
Verify if the device can receive cellular network connectivityAttempt to make/receive a call, send SMS, or use mobile data. The vulnerability is triggered when processing incoming NAS messages from the EMM layer during normal cellular communicationAffected if The device connects to a cellular network (LTE/5G) and the modem has not been patched; the vulnerability applies to all NAS message processing
-
Check vendor security bulletins for modem firmware updatesSearch the device manufacturer's security advisory page or your carrier's update documentation for CVE-2022-20210 or 'modem NAS parsing'Affected if No vendor acknowledgment or patch exists for this specific CVE in the available firmware releases
A user is affected if their Android device uses a cellular modem with unpatched firmware that has not received the vendor-specific update addressing the NAS message parsing vulnerability.
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.
From vendor dataApply vendor-provided modem firmware updates. Organizations should inventory affected Android devices and coordinate with device manufacturers/carriers for patch deployment.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20210 — 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-20210 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