CVE-2020-14100
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 · uneditedIn Xiaomi router R3600 ROM version<1.0.66, filters in the set_WAN6 interface can be bypassed, causing remote code execution. The router administrator can gain root access from this vulnerability.
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 confidenceThe Xiaomi R3600 router has a filter bypass vulnerability in the set_WAN6 interface in firmware versions prior to 1.0.66. An attacker can exploit this to bypass security filters and achieve remote code execution with root privileges, effectively giving the router administrator full root access to the device.
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< 1.0.66CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Xiaomi R3600Locate the router model identifier on the device physical label or in the administrative web interface system status pageAffected if The device is not a Xiaomi R3600 model router (not affected)
-
Identify the installed firmware versionAccess the router administrative web interface, navigate to the System or Status section, and locate the firmware version field; alternatively, check via command line if SSH/telnet access is availableAffected if Unable to determine the firmware version (further investigation required)
-
Compare firmware version against affected rangeReview the identified firmware version number and compare it to the vulnerable range: any version prior to 1.0.66Affected if Firmware version is 1.0.65 or lower (the router is affected by the vulnerability)
-
Verify set_WAN6 interface accessibilityCheck if the set_WAN6 interface is accessible from the WAN side or if remote administration is enabled; this typically requires examining the router's firewall settings and remote management configurationAffected if The set_WAN6 interface is exposed to untrusted networks and the firmware is below 1.0.66
The environment is affected if the device is a Xiaomi R3600 router running firmware version 1.0.65 or lower with the set_WAN6 interface accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.66
Upgrade Xiaomi R3600 firmware to version 1.0.66 or later to remediate the filter bypass vulnerability in the set_WAN6 interface.
Firmware version 1.0.66
- Access the Xiaomi R3600 router administration interface via web browser (typically at 192.168.31.1 or miwifi.com)
- Navigate to the firmware upgrade or system settings section
- Download the official firmware version 1.0.66 or later from Xiaomi's official support site (privacy.mi.com)
- Upload the firmware file and initiate the upgrade process
- Wait for the router to complete the firmware flash and reboot automatically
- Verify the firmware version has been updated to 1.0.66 or higher in the router admin panel
- Reconfigure any custom settings that may have been reset after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14100 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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