dbcve.org
Mh702x FirmwareOperating system · Motorola

CVE-2021-3460

CRITICAL · 9.8 CVSS v3.1 Published 2021-04-13
Fix available
A fix is available. Upgrade to 2.0.0.301 or later.
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
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.

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

The Motorola MH702x devices fail to properly validate the server certificate when communicating with the support server, allowing a man-in-the-middle attacker to intercept or modify traffic between the device and support server. This certificate validation bypass could enable credential theft, firmware tampering, or injection of malicious responses.

MitigationUpgrade Motorola MH702x devices to firmware version 2.0.0.301 or later which implements proper server certificate verification. If immediate upgrade is not possible, ensure device management network segments are isolated to reduce MITM attack surface.

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
Mh702x FirmwareOperating system
Affected:< 2.0.0.301

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.1/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 web interface or check the device label to confirm it is a Motorola MH702x model.
    Affected if Device is not a Motorola MH702x product.
  2. Determine firmware version
    Log into the device admin interface and navigate to the Status or System Information page to view the installed firmware version.
    Affected if Firmware version is lower than 2.0.0.301.
  3. Check device network configuration
    Inspect the device network settings to determine if it is configured to communicate with an external support server.
    Affected if The device is configured to reach an external support server and the firmware version is below 2.0.0.301.

The environment is affected if the device is a Motorola MH702x running firmware version below 2.0.0.301 and is configured to communicate with a support server.

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
Upgrade available Upgrade to 2.0.0.301 or later
Fixed in 2.0.0.301
Interim mitigation

Upgrade Motorola MH702x devices to firmware version 2.0.0.301 or later which implements proper server certificate verification. If immediate upgrade is not possible, ensure device management network segments are isolated to reduce MITM attack surface.

Recommended fix High confidence

Firmware version 2.0.0.301

  1. Access the Motorola MH702x router web interface by navigating to its IP address (typically 192.168.0.1 or 192.168.1.1) in a web browser
  2. Log in with administrator credentials
  3. Locate the firmware upgrade section, typically found under 'Administration', 'System', or 'Maintenance' settings
  4. Download the firmware version 2.0.0.301 from the official Motorola Mentor support site (motorolamentor.zendesk.com) or official Motorola support channels
  5. In the firmware upgrade interface, upload the downloaded firmware file (2.0.0.301)
  6. Wait for the upload to complete and the device to reboot - do not power off the device during this process
  7. After the device restarts, verify the firmware version has been updated to 2.0.0.301 or later in the system information settings
  8. Confirm that the device is functioning normally and all connectivity is restored

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

Fix this in Mh702x Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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