CVE-2020-11960
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 · uneditedXiaomi router R3600 ROM before 1.0.50 is affected by a vulnerability when checking backup file in c_upload interface let attacker able to extract malicious file under any location in /tmp, lead to possible RCE and DoS
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 contains a path traversal vulnerability in the c_upload interface when processing backup files. The firmware lacks proper input validation allowing attackers to write malicious files to arbitrary locations within /tmp through manipulated file paths in the backup upload mechanism. This can lead to remote code execution or denial of service.
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.20CVSS 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 router modelAccess the router web interface or check the device label to verify the model is Xiaomi R3600Affected if Device is not a Xiaomi R3600 router - different models are not affected by this CVE
-
Check firmware versionLog into the router web interface and navigate to the firmware or status page to view the current firmware version. Compare against the affected range: < 1.0.20Affected if Firmware version is less than 1.0.20 - versions below this threshold contain the vulnerability
-
Verify web management interface accessibilityDetermine if the router web management interface (HTTP/HTTPS on ports 80 or 443) is reachable from network segments where untrusted devices operateAffected if Web interface is exposed to untrusted networks - this is the attack vector for the path traversal flaw
-
Confirm backup upload feature availabilityAccess the router web interface and locate the backup/restore configuration functionality, typically found under Settings, Administration, or System settingsAffected if Backup upload interface is accessible - the c_upload endpoint processes the malicious backup files containing path traversal sequences
A Xiaomi R3600 router running firmware version below 1.0.20 with its web management and backup upload interfaces accessible to untrusted networks is affected by this vulnerability.
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.20
Upgrade Xiaomi R3600 firmware to version 1.0.50 or later to remediate this vulnerability. Until patched, restrict access to the router's web management interface from untrusted networks.
Firmware version 1.0.50 or later
- 1. Access the Xiaomi R3600 router administration interface via web browser (typically at 192.168.31.1)
- 2. Navigate to the firmware update or system settings section
- 3. Check the current firmware version under system information
- 4. Download the latest stable firmware from Xiaomi's official support page for the R3600 model
- 5. Upload and apply the firmware update, ensuring continuous power during the process
- 6. After reboot, verify the new firmware version is 1.0.50 or later
- 7. Confirm the c_upload interface no longer allows arbitrary file extraction
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11960 — 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-11960 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