dbcve.org
Ax3600 FirmwareOperating system · Mi

CVE-2020-14109

HIGH · 7.2 CVSS v3.1 Published 2021-09-16
Fix available
A fix is available. Upgrade to after 1.1.12 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
There is command injection in the meshd program in the routing system, resulting in command execution under administrator authority on Xiaomi router AX3600 with ROM version =< 1.1.12

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 confidence

Command injection vulnerability in the meshd routing daemon on Xiaomi AX3600 routers (ROM <= 1.1.12) allows authenticated or adjacent attackers to inject and execute arbitrary operating system commands with administrator/root privileges due to insufficient input validation.

MitigationUpdate Xiaomi AX3600 firmware to a version newer than 1.1.12; if patching is not immediately possible, restrict network access to the meshd service and disable remote administration interfaces.

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.1.12

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify router model
    Access the router admin interface or check the device label to confirm the model is Xiaomi AX3600
    Affected if Device is not a Xiaomi AX3600 (different models are not affected by this specific CVE)
  2. Check firmware version
    Log into the router admin panel and navigate to Status or Settings > Firmware Version, or use the miwifi command-line tool if accessible, to determine the installed firmware version number
    Affected if Firmware version is 1.1.12 or lower
  3. Locate meshd service
    On the router filesystem (via SSH if enabled), check for the presence and status of the meshd binary, typically found in /usr/sbin/meshd or similar system daemon directories
    Affected if The meshd service is present and running on the device
  4. Verify remote administration access
    Check router settings for remote management/remote access features (often under Settings > Administration or Security settings); determine if the web interface or meshd is exposed to WAN or untrusted networks
    Affected if Remote administration interfaces are enabled or the router is directly exposed to untrusted networks
  5. Confirm authentication status
    Review whether default administrator credentials remain in use or if the router's management interface is accessible without authentication from adjacent network segments
    Affected if The router management interface is accessible to unauthenticated or adjacent attackers

The environment is affected if the device is a Xiaomi AX3600 running firmware version 1.1.12 or lower, with the meshd service accessible to authenticated or adjacent attackers.

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 a release after 1.1.12
Interim mitigation

Update Xiaomi AX3600 firmware to a version newer than 1.1.12; if patching is not immediately possible, restrict network access to the meshd service and disable remote administration interfaces.

Recommended fix Moderate confidence

Any firmware version > 1.1.12 (contact Xiaomi support or check official Xiaomi router support pages for the specific stable release containing the fix)

  1. 1. Access the Xiaomi router AX3600 web management interface or use the Mi WiFi app
  2. 2. Navigate to the firmware update section (usually under Settings > Hardware Settings > Firmware Update or similar)
  3. 3. Check the current firmware version (should be <= 1.1.12 if vulnerable)
  4. 4. Initiate a firmware update to obtain the latest stable version
  5. 5. Verify the update was successful and confirm the new firmware version is > 1.1.12
  6. 6. Restart the router to ensure all services, including meshd, are running with the updated firmware
Caveat Review release notes for any configuration or feature changes between versions; backup router configuration before upgrading

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

Fix this in Ax3600 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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