Xiaomi R3600 FirmwareOperating system · Mi

CVE-2020-14095

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-24
Fix available
A fix is available. Upgrade to 1.0.20 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
In Xiaomi router R3600, ROM version<1.0.20, a connect service suffers from an injection vulnerability through the web interface, leading to a stack overflow or remote code execution.

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

The Xiaomi R3600 router contains an injection vulnerability in the connect service accessible through the web interface. This flaw allows attackers to inject malicious input that triggers a stack overflow, potentially leading to remote code execution. The vulnerability affects ROM versions prior to 1.0.20.

MitigationUpgrade the router's firmware to ROM version 1.0.20 or later to patch the injection vulnerability. If upgrading is not immediately possible, restrict web interface access to trusted networks or disable remote administration.

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
Xiaomi R3600 FirmwareOperating system
Affected:< 1.0.20

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. Check the router's firmware version
    Log into the Xiaomi R3600 web admin interface (typically at 192.168.31.1) and navigate to Status or System Settings to view the current ROM version. Alternatively, check via command line using `cat /proc/xiaoqiang/rom_version` if you have shell access.
    Affected if The displayed ROM version is below 1.0.20 (e.g., 1.0.19, 1.0.18, etc.)
  2. Verify the web interface is accessible
    Confirm the router's HTTP/HTTPS web administration interface is reachable. Try accessing the router's IP address from a browser. The vulnerability exists in the connect service within this web interface.
    Affected if The web interface responds and is reachable from your testing location
  3. Check if remote web administration is enabled
    In the router's web UI, look for settings under Administration, System, or Network settings that control remote access or remote web management. This setting determines whether the interface is accessible from outside the local network.
    Affected if Remote administration is enabled, allowing the vulnerable web interface to be reached from external networks

You are affected if your Xiaomi R3600 router runs firmware version lower than 1.0.20 AND the web interface (specifically the connect service) is accessible, either locally or remotely.

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 1.0.20 or later
Fixed in 1.0.20
Interim mitigation

Upgrade the router's firmware to ROM version 1.0.20 or later to patch the injection vulnerability. If upgrading is not immediately possible, restrict web interface access to trusted networks or disable remote administration.

Recommended fix High confidence

Firmware 1.0.20 or later

  1. Access the Xiaomi R3600 router administration interface via web browser
  2. Navigate to the firmware update or system settings section
  3. Download the firmware version 1.0.20 or later from the official Xiaomi support site (mi.com or router product page)
  4. Upload and apply the firmware update through the web interface
  5. Allow the router to complete the update process and reboot automatically
  6. Verify the firmware version has been updated to 1.0.20 or higher after reboot
Caveat Standard security update; backup router configuration before upgrading as a precaution

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

Fix this in Xiaomi R3600 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-14095 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