CVE-2023-20819
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 CDMA PPP protocol, there is a possible out of bounds write due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privilege needed. User interaction is not needed for exploitation. Patch ID: MOLY01068234; Issue ID: ALPS08010003.
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 missing bounds check in the CDMA PPP (Point-to-Point Protocol) implementation allows an out-of-bounds memory write. This memory corruption vulnerability can be exploited remotely without user interaction, potentially leading to privilege escalation. The issue is traced to patch ID MOLY01068234.
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 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 hardware modelCheck the device documentation, system information, or modem AT commands (e.g., AT+CGMM or AT+CGMI) to determine if the hardware is a Mediatek Lr11, Lr12a, Lr13, Nr15, Nr16, or Nr17 device.Affected if The device is a Mediatek Lr11, Lr12a, Lr13, Nr15, Nr16, or Nr17 modem.
-
Confirm firmware version rangeQuery the modem firmware version using AT commands (e.g., AT+CGMR) or through the host system interface. Compare the version to the affected product list.Affected if The firmware corresponds to any version of Mediatek Lr11, Lr12a, Lr13, Nr15, Nr16, or Nr17.
-
Verify CDMA PPP functionality is enabledCheck the modem configuration or network settings for active CDMA PPP connections. Look for PPP-related interfaces, dial-up profiles, or CDMA network registrations in the system logs or configuration files.Affected if CDMA PPP functionality is actively enabled or configured on the device.
-
Assess network exposureReview network traffic monitoring or firewall rules to determine if PPP traffic (typically on serial interfaces) can be received from untrusted sources or if the CDMA modem has direct network exposure.Affected if The CDMA PPP interface is reachable from network or handles external PPP traffic.
If the device uses Mediatek Lr11, Lr12a, Lr13, Nr15, Nr16, or Nr17 firmware with CDMA PPP enabled and exposed to network traffic, the environment is affected by this 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 the vendor patch (MOLY01068234). If unavailable, consider network-level filtering of PPP traffic or disabling CDMA PPP functionality to reduce attack surface while a fix is developed.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20819 — 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-2023-20819 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