CVE-2020-14111
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 · uneditedA command injection vulnerability exists in the Xiaomi Router AX3600. The vulnerability is caused by a lack of inspection for incoming data detection. Attackers can exploit this vulnerability to execute code.
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 confidenceCommand injection vulnerability in Xiaomi Router AX3600 due to insufficient input validation on incoming data, allowing attackers to execute arbitrary code on 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.1.15CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify router modelAccess router admin panel or check device label/marketing materials to confirm the model is Xiaomi AX3600 or Mi AX3600Affected if Device is not a Xiaomi AX3600 model
-
Check installed firmware versionLog into router admin panel (typically 192.168.31.1 or 192.168.1.1), navigate to Status or Settings > Firmware Version. Alternatively, check via CLI if accessible: cat /etc/config/version or similarAffected if Firmware version is lower than 1.1.15 (e.g., 1.0.14, 1.1.10, etc.)
-
Verify remote management is enabledIn router admin panel, check Settings > Security or Settings > Remote Management. Look for options like 'Remote Access', 'External Access', or 'WAN Access' that allow management from internetAffected if Remote management interface is exposed to WAN (internet-facing)
-
Check for exposed management servicesScan router WAN IP for open management ports (typically HTTP 80, HTTPS 443, SSH 22, or vendor-specific ports). Use external port scanner or check router firewall settingsAffected if Management ports are accessible from internet without VPN/segmentation
User is affected if they have a Xiaomi AX3600 router running firmware version below 1.1.15 AND the router's management interface is exposed to the network where an attacker can send malicious input.
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.1.15
Apply vendor firmware patch when available; if unavailable, implement network segmentation, disable remote management interfaces, or consider device replacement.
1.1.15
- Download the official Xiaomi Router AX3600 firmware version 1.1.15 or later from the official Xiaomi support portal or trust.mi.com
- Access the router's web management interface by entering the router's IP address in a web browser
- Log in with administrator credentials
- Navigate to the firmware upgrade or system settings section
- Select the downloaded firmware file and initiate the upgrade process
- Wait for the upgrade to complete and the router to reboot automatically
- Verify the firmware version has been updated to 1.1.15 or later after the reboot
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-14111 — 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-14111 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