dbcve.org
Ax3600 FirmwareOperating system · Mi

CVE-2020-14115

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 1.0.67 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
A 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 confidence

A command injection vulnerability exists in the Xiaomi Router AX3600 due to insufficient validation of incoming data. Attackers can inject arbitrary operating system commands through unsanitized input fields, achieving remote code execution with high privileges on the affected device.

MitigationApply the latest firmware update from Xiaomi for the AX3600 router. If no update is available, restrict network access to the router's management interface using firewall rules or ACLs to limit exposure to trusted sources only.

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
Ax3600 FirmwareOperating system
Affected:< 1.0.67

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 current firmware version
    Access the router's web management interface (typically at 192.168.31.1) and navigate to Settings > Status, or log in via SSH and run the command 'cat /proc/version' or 'nvram get firmware_version' to retrieve the installed firmware version
    Affected if The firmware version is less than 1.0.67 (for example, 1.0.56, 1.0.30, etc.)
  2. Verify if the web management interface is accessible
    Confirm whether the router's HTTP/HTTPS management port (80/443) is reachable from untrusted networks. Check router firewall settings or run a port scan against the router's WAN IP address
    Affected if The web management interface is exposed to the internet or untrusted LAN segments without ACL restrictions
  3. Check for unauthorized processes or command injection artifacts
    If you have SSH access, run 'ps' to list running processes and look for unexpected binaries, or check /tmp and /var directories for unfamiliar scripts or executables
    Affected if Unexpected processes are running, or unfamiliar scripts are present in temporary directories
  4. Review authentication logs for suspicious activity
    If available, check system logs via 'logread' or the web UI logs section for failed login attempts followed by unusual requests, or for commands originating from unexpected IP addresses
    Affected if Logs show authentication attempts followed by suspicious or malformed requests, especially from external IP addresses

Your environment is affected if the Xiaomi AX3600 router is running firmware version 1.0.67 or lower and the management interface is accessible to untrusted users.

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.67 or later
Fixed in 1.0.67
Interim mitigation

Apply the latest firmware update from Xiaomi for the AX3600 router. If no update is available, restrict network access to the router's management interface using firewall rules or ACLs to limit exposure to trusted sources only.

Recommended fix Moderate confidence

Firmware version 1.0.67 or later

  1. Access the Xiaomi Router AX3600 web management interface or Mi WiFi app
  2. Navigate to the firmware settings or system update section
  3. Check the current firmware version under settings or status
  4. If the current version is below 1.0.67, initiate a firmware update
  5. If automatic update is available, allow the router to download and install the latest firmware
  6. If automatic update is not available, download the official firmware 1.0.67 or later from trust.mi.com or the official Xiaomi support site
  7. Manually upload the firmware file through the router's web interface or recovery mode
  8. Wait for the update to complete and the router to reboot

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

Fix this in Ax3600 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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