CVE-2022-21744
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 Modem 2G RR, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution when decoding GPRS Packet Neighbour Cell Data (PNCD) improper neighbouring cell size with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00810064; Issue ID: ALPS06641626.
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 buffer overflow vulnerability exists in the 2G modem's Radio Resource (RR) layer when decoding GPRS Packet Neighbour Cell Data (PNCD). The missing bounds check during processing of neighboring cell size data allows an out-of-bounds write, enabling remote code execution without user interaction or elevated privileges.
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 versionsall versionsall versionsall versionsall versionsall versionsall 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 the modem chipsetCheck device specifications, AT command output (e.g., AT+CGMM, AT+CGMI), or system logs to determine if the device uses a Mediatek modem from the affected series: Lr11, Lr12, Lr12a, Lr13, Lr9, Nr15, or Nr16Affected if The device contains any of the listed Mediatek modem chipsets (Lr11, Lr12, Lr12a, Lr13, Lr9, Nr15, Nr16)
-
Check modem firmware versionQuery the modem firmware version using AT commands such as AT+CGMR or through device system information if accessibleAffected if The modem firmware version is earlier than the patched version MOLY00810064, or if the version cannot be determined and the chipset is on the affected list
-
Verify 2G network capability is enabledCheck device network settings, modem configuration, or AT commands (e.g., AT+CNMP, AT+CGEG) to determine if 2G/GPRS radio access is enabled on the deviceAffected if 2G/GPRS network support is enabled on the device - this is required for the vulnerable RR layer code path to be exercised
-
Inspect network registration behaviorMonitor modem logs or use AT+CREG? / AT+CGREG? commands to observe if the device registers on GPRS networks or if 2G cell scanning occursAffected if The device actively scans for or connects to 2G/GPRS cells, exposing the vulnerable PNCD decoding code path
A device is affected if it contains any of the listed Mediatek modem chipsets (Lr11, Lr12, Lr12a, Lr13, Lr9, Nr15, Nr16), operates with 2G/GPRS enabled, and does not have firmware version MOLY00810064 or later applied.
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 the vendor firmware patch (MOLY00810064) to update the modem/baseband firmware. Since this is a low-level modem vulnerability, end users cannot remediate independently; they must obtain a firmware update from their device vendor or mobile carrier.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21744 — 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-21744 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