dbcve.org
Mf920 FirmwareOperating system · Zte

CVE-2019-3412

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
All versions up to BD_R218V2.4 of ZTE MF920 product are impacted by command execution vulnerability. Due to some interfaces do not adequately verify parameters, an attacker can execute arbitrary commands through specific interfaces.

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

Command injection vulnerability in ZTE MF920 wireless mobile hotspot devices. Certain interfaces fail to adequately validate input parameters, allowing remote attackers to execute arbitrary operating system commands on the device through crafted requests.

MitigationApply vendor firmware update beyond BD_R218V2.4 if available. If no patch exists, disable or restrict access to vulnerable interfaces via network segmentation, firewall rules, or consider device replacement.

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
Mf920 FirmwareOperating system
Affected:< bd_r218v2.4

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
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Identify device model
    Access the device admin interface or check the device label/marketing to confirm the model is ZTE MF920
    Affected if Device is not a ZTE MF920 model - different models are not affected by this specific CVE
  2. Check firmware version
    Log into the device admin panel (typically at 192.168.0.1 or 192.168.1.1) and navigate to Status or Device Information to view the firmware version
    Affected if Firmware version is below bd_r218v2.4 (for example, bd_r218v2.0, bd_r218v1.x, or any version string that lexicographically precedes 'bd_r218v2.4')
  3. Verify management interface accessibility
    Attempt to access the device web admin interface from an external network position using the device's public IP or check firewall rules that allow HTTP/HTTPS access to the device
    Affected if The device admin interface is reachable from untrusted networks (internet-facing) or from internal network segments where untrusted users could send crafted requests

You are affected if the device is a ZTE MF920 with firmware version lower than bd_r218v2.4 and the vulnerable management interface is accessible to attackers on the network.

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 vendor firmware update beyond BD_R218V2.4 if available. If no patch exists, disable or restrict access to vulnerable interfaces via network segmentation, firewall rules, or consider device replacement.

Recommended fix Moderate confidence

BD_R218V2.4 or later firmware version

  1. 1. Identify the current firmware version of the ZTE MF920 device by accessing the web management interface or checking device documentation.
  2. 2. Navigate to the ZTE support portal at support.zte.com.cn to download the latest firmware version.
  3. 3. Locate and download firmware version BD_R218V2.4 or later from the official ZTE support site.
  4. 4. Access the device's administrative web interface using a browser.
  5. 5. Navigate to the firmware upgrade section (typically under Settings > Firmware Update or Administration > Software Update).
  6. 6. Upload the downloaded firmware file (BD_R218V2.4 or later) and initiate the upgrade process.
  7. 7. Wait for the upgrade to complete - do not power off the device during this process.
  8. 8. After reboot, verify the new firmware version is installed correctly.
Caveat Firmware upgrades may reset device configuration to defaults; ensure backup of settings before upgrading

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

Fix this in Mf920 Firmware 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-2019-3412 — 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-2019-3412 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