dbcve.org
Nr15Operating system · Mediatek

CVE-2024-20070

MEDIUM · 5.1 CVSS v3.1 Published 2024-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
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, there is a possible information disclosure due to using risky cryptographic algorithm during connection establishment negotiation. This could lead to remote information disclosure, when weak encryption algorithm is used, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00942482; Issue ID: MSV-1469.

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

This vulnerability exists in a modem component where risky/weak cryptographic algorithms are used during connection establishment negotiation. An attacker on the network path could potentially intercept or decrypt communications due to the use of weak encryption, leading to remote information disclosure without requiring any additional privileges or user interaction.

MitigationApply the vendor patch (MOLY00942482) to update the modem firmware and remove weak cryptographic algorithms. If immediate patching is not feasible, implement network-level controls such as TLS inspection or VPN tunnels to protect communications traversing the affected 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 data
Nr15Operating system
Affected:all versions
Nr16Operating system
Affected:all versions
Nr17Operating 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 Mediatek modem presence
    Inventory your hardware or firmware to determine if any devices or components use Mediatek Nr15, Nr16, or Nr17 modem chipsets. Check system documentation, hardware specs, or firmware binaries for these model identifiers.
    Affected if Any device in your environment contains a Mediatek Nr15, Nr16, or Nr17 modem component.
  2. Locate modem firmware version
    Access the modem firmware information through device management interfaces, diagnostic logs, or by querying the modem subsystem via AT commands (if supported). Look for firmware version strings or build numbers.
    Affected if The modem firmware version corresponds to Mediatek Nr15, Nr16, or Nr17 product lines (all versions are affected).
  3. Verify active modem configuration
    Check if the affected modem component is actively configured, enabled, or currently handling network connections. Review network interface status, connection logs, or carrier configuration files.
    Affected if The Mediatek Nr15/Nr16/Nr17 modem is actively handling communications or is the primary path for network traffic.
  4. Inspect crypto negotiation settings
    Review modem or network configuration for negotiated cipher suites, cryptographic algorithms, or security protocol settings used during connection establishment. Look for indicators of legacy or weak algorithms (e.g., older SSL/TLS versions, deprecated ciphers).
    Affected if Weak or risky cryptographic algorithms are being negotiated or used by the modem for connection establishment.

Your environment is affected if you have any actively used Mediatek Nr15, Nr16, or Nr17 modem components, since all versions of these products contain the weak cryptographic algorithm 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 (MOLY00942482) to update the modem firmware and remove weak cryptographic algorithms. If immediate patching is not feasible, implement network-level controls such as TLS inspection or VPN tunnels to protect communications traversing the affected modem.

Fix this in Nr15 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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