dbcve.org
AndroidOperating system · Google

CVE-2023-32889

HIGH · 7.5 CVSS v3.1 Published 2024-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In 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: MOLY01161825; Issue ID: MOLY01161825 (MSV-895).

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 confidence

A missing bounds check in the Modem IMS Call UA (User Agent) component allows an out-of-bounds write, leading to remote denial of service. The vulnerability is exploitable without user interaction or elevated privileges, indicating a network-adjacent attack vector targeting the IMS (IP Multimedia Subsystem) signaling layer.

MitigationApply the vendor patch MOLY01161825 through appropriate firmware or software updates from the affected device vendor. If immediate patching is not possible, consider network-level controls to limit exposure of the IMS signaling interfaces.

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 data
AndroidOperating system
Affected:= 11.0= 12.0= 13.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Run 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android version
    Affected if The installed version is exactly 11.0, 12.0, or 13.0 (these are the only affected versions listed)
  2. Confirm device has IMS capability
    Check if the device supports IMS (IP Multimedia Subsystem) by examining 'getprop ro.telephony.ims_supported' or checking device specifications for IMS support
    Affected if IMS is supported and enabled on the device (the vulnerability exists in the IMS Call UA component)
  3. Verify IMS Call UA service is running
    Check running modem processes related to IMS: 'ps -A | grep -i ims' or examine the modem/radio process list via 'getprop | grep radio'
    Affected if IMS-related services are active (the vulnerable component is loaded and running)
  4. Check modem firmware patch level
    Query modem firmware version via AT command 'AT+CGMR' or through manufacturer-specific diagnostic tools if available
    Affected if Modem firmware predates patch MOLY01161825 or cannot be verified (indicates unpatched modem)

The device is likely affected if it runs Android 11.0, 12.0, or 13.0 with an active IMS stack and the modem firmware has not received the MOLY01161825 patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch MOLY01161825 through appropriate firmware or software updates from the affected device vendor. If immediate patching is not possible, consider network-level controls to limit exposure of the IMS signaling interfaces.

Recommended fix Moderate confidence

Android security patch level incorporating MediaTek bulletin (MOLY01161825) - typically included in monthly Android Security Patch releases

  1. 1. Check with your device OEM or carrier for the availability of the security patch containing the MediaTek fix (Patch ID: MOLY01161825)
  2. 2. Apply the latest Android security update for your device once released by your OEM/carrier
  3. 3. Verify the Android security patch level is at or after the date that includes the fix for CVE-2023-32889
  4. 4. On supported devices, ensure Android Enterprise or MDM configurations are updated to require mandatory security patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32889 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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