CVE-2023-32874
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 IMS Stack, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01161803; Issue ID: MOLY01161803 (MSV-893).
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 confidenceThis vulnerability in the Modem IMS (IP Multimedia Subsystem) Stack contains an out-of-bounds write due to a missing bounds check. An attacker can exploit this memory corruption flaw to achieve remote code execution without requiring any user interaction or elevated privileges. The vulnerability affects the modem firmware layer, making it exploitable via network communications processed by the modem.
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 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 modelCheck device specifications, modem firmware details, or use AT commands (e.g., AT+CGMM or AT+CGMR) to query the modem chipset identifierAffected if The chipset model is Lr13, Nr15, Nr16, or Nr17 (all versions of these families are affected)
-
Verify modem firmware versionQuery the modem firmware version using AT commands such as AT+CGMR or through device diagnostic menusAffected if The device runs Mediatek modem firmware on an affected chipset family (any version since all versions are vulnerable)
-
Confirm IMS stack is in useCheck if the device uses VoLTE, VoNR, or other IMS-based services by examining modem configuration or network settingsAffected if IMS functionality is enabled and the device uses one of the affected Mediatek modem chipsets
-
Review network-facing modem interfacesExamine modem logs or network traffic handled by the modem to identify if IMS messages are processedAffected if The modem processes IMS-related network communications and operates on an affected Mediatek chipset
A device is affected if it contains a Mediatek modem chipset from the Lr13, Nr15, Nr16, or Nr17 family, regardless of firmware version, and utilizes IMS functionality for voice or multimedia services.
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 MOLY01161803 through firmware update from the device manufacturer. Since this is a modem firmware vulnerability, end users must obtain updated firmware from their device/OEM vendors.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.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 $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32874 — 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-32874 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