dbcve.org
Nr15Operating system · Mediatek

CVE-2024-20004

HIGH · 7.5 CVSS v3.1 Published 2024-02-05
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 NL1, there is a possible system crash due to an improper input validation. This could lead to remote denial of service, if NW sent invalid NR RRC Connection Setup message, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01191612; Issue ID: MOLY01195812 (MSV-985).

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 confidence

This vulnerability exists in Modem NL1 where improper input validation of NR RRC Connection Setup messages allows a remote network attacker to cause a system crash. The modem fails to properly validate incoming RRC connection setup messages, leading to a denial of service condition when malformed messages are received.

MitigationApply the vendor patch (MOLY01191612) to the modem firmware. Until the patch is deployed, monitor for modem crashes and coordinate with the mobile network operator to ensure network-side integrity.

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
Nr15Operating system
Affected:all versions

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. Identify the modem chipset in use
    Check the device specifications or modem firmware information to confirm it uses a Mediatek Nr15 (Nr15) modem chipset. This can typically be found in device docs, modem info (*#*#4636#*#* on Android), or system logs.
    Affected if The device does not have a Mediatek Nr15 chipset - if it uses a different modem, this CVE does not apply.
  2. Determine the installed modem firmware version
    Access the modem firmware version through AT commands (AT+CGMR or ATI), device engineering mode, or by reading the modem partition from the device. Record the full firmware build number.
    Affected if The modem firmware version is known and can be compared to the patched version - all unpatched versions of Mediatek Nr15 are affected.
  3. Compare firmware to the patched version MOLY01191612
    Compare the installed modem firmware version against the patched build identifier MOLY01191612. If the installed version is lower or lacks this specific patch identifier, the vulnerability is present.
    Affected if The installed version is earlier than MOLY01191612 or does not contain the MOLY01191612 patch identifier.
  4. Review modem crash logs for NR RRC-related failures
    Examine modem crash dumps, kernel logs (dmesg), or device bugreports for entries containing 'NR RRC', 'RRC Connection Setup', or modem restart/crash indicators. Look for unexpected modem resets or 'modem crashed' events.
    Affected if Crash logs show repeated modem crashes correlated with NR RRC Connection Setup message processing, indicating potential exploitation.

If the device uses a Mediatek Nr15 modem and the installed firmware version is earlier than or does not contain the MOLY01191612 patch, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (MOLY01191612) to the modem firmware. Until the patch is deployed, monitor for modem crashes and coordinate with the mobile network operator to ensure network-side integrity.

Fix this in Nr15 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20004 — 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-2024-20004 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