CVE-2022-20083
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/3G CC, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution when decoding combined FACILITY with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00803883; Issue ID: MOLY00803883.
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 confidenceIn Modem 2G/3G Call Control (CC), a missing bounds check when decoding combined FACILITY messages allows an out-of-bounds write, enabling remote code execution without requiring user interaction or additional 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 Mediatek modem chipset in useCheck device specifications, AT command interface, or system logs for the modem chipset model (Mediatek Lr9, Lr11, Lr12, Lr12a, Lr13, Nr15, or Nr16)Affected if Device uses any of the listed Mediatek modem chipsets (Lr9, Lr11, Lr12, Lr12a, Lr13, Nr15, Nr16)
-
Check modem firmware versionQuery modem firmware version via AT command (e.g., AT+CGMR or vendor-specific command) and compare against the patched version MOLY00803883Affected if Modem firmware version is unknown or earlier than the patched version MOLY00803883
-
Verify 2G/3G Call Control is enabledCheck if the device has 2G or 3G network capability enabled and active - examine modem settings, network mode configuration, or AT+CNMP command outputAffected if 2G or 3G calling/control plane is enabled on the device
-
Check for combined FACILITY message processingThis is a protocol-level condition that is difficult to detect directly without access to modem debug logs or traffic analysis - look for any modem crash logs, memory dumps, or unexpected restarts that may indicate exploitationAffected if Modem exhibits unexpected behavior, crashes, or memory corruption events, especially during 2G/3G call setup involving FACILITY messages
Device is affected if it uses any Mediatek modem chipset (Lr9, Lr11, Lr12, Lr12a, Lr13, Nr15, Nr16) with firmware versions prior to MOLY00803883 and has 2G/3G Call Control enabled.
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 patch (MOLY00803883) by updating the modem firmware to the patched version. If no update is available, contact the device/vendor for patched modem firmware.
- Consultation8.0 h
- Implementation4.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 $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20083 — 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-20083 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