CVE-2023-32888
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 Call UA, there is a possible out of bounds write due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01161830; Issue ID: MOLY01161830 (MSV-894).
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 confidenceAn out-of-bounds write vulnerability exists in the Modem IMS Call User Agent component due to a missing bounds check. This allows remote attackers to cause a denial of service condition without requiring any 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 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 modelCheck system or device information for the presence of a Mediatek modem. On Linux, this may involve checking 'AT+CGMM' AT command output, system logs, or /proc/cpuinfo. On Android, check 'getprop' for mediatek hardware details.Affected if The device contains a Mediatek Nr15, Nr16, or Nr17 modem chip.
-
Confirm modem firmware versionQuery the modem firmware version via AT command (such as 'AT+CGMR' or vendor-specific commands) or through system information APIs provided by the device OEM.Affected if The modem firmware version corresponds to the Mediatek Nr15, Nr16, or Nr17 platform.
-
Verify IMS Call User Agent componentCheck if the Modem IMS Call UA feature is present and enabled on the device. This may be indicated in modem configuration settings, baseband logs, or through AT command responses related to IMS (such as 'AT+CIUTEST' or similar IMS registration queries).Affected if The IMS Call User Agent component is active on the Mediatek Nr15/Nr16/Nr17 modem.
-
Check for vulnerable configurationExamine modem or baseband configuration for settings related to IMS call handling. The vulnerability exists when the IMS Call UA processes certain inputs without proper bounds checking.Affected if The device uses Mediatek Nr15/Nr16/Nr17 baseband with IMS enabled, as all versions of these platforms are affected by the missing bounds check.
If the device or system incorporates a Mediatek Nr15, Nr16, or Nr17 modem with the IMS Call User Agent component enabled, 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 vendor patch MOLY01161830 to update the Modem IMS Call UA firmware and remediate the missing bounds check. As this is a modem/baseband component, firmware updates must be obtained from the device/vendor and deployed to affected systems.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32888 — 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-32888 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