CVE-2020-14101
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 · uneditedThe data collection SDK of the router web management interface caused the leakage of the token. This affects Xiaomi router AX1800rom version < 1.0.336 and Xiaomi route RM1800 root version < 1.0.26.
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 confidenceA token leakage vulnerability exists in the data collection SDK of the Xiaomi router AX1800 (rom version < 1.0.336) and RM1800 (root version < 1.0.26) web management interface. The vulnerability allows unauthenticated attackers to potentially obtain sensitive session tokens through the data collection component.
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.336< 1.0.26CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 modelCheck the physical device label or log into the web management interface to confirm the exact model number (AX1800 or RM1800)Affected if Model is Mi AX1800 or Mi RM1800
-
Check AX1800 firmware versionLog into the router web interface (typically at 192.168.31.1) and navigate to Status or System Settings to view the current firmware version, or run command 'nvram get ver' via SSH if availableAffected if Firmware version is below 1.0.336 on AX1800
-
Check RM1800 firmware versionLog into the router web interface and navigate to Status or System Settings to view the current firmware version, or run command 'nvram get ver' via SSH if availableAffected if Firmware version is below 1.0.26 on RM1800
-
Verify web management interface exposureCheck if the router web management interface (port 80/443) is accessible from the internet or untrusted network segments by reviewing firewall rules and port forwardingsAffected if Web management interface is exposed to untrusted networks
A user is affected if they are running Xiaomi AX1800 firmware below 1.0.336 or RM1800 below 1.0.26 AND the router web management interface is accessible from an untrusted network.
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.
From vendor data1.0.261.0.336
Update Xiaomi router AX1800 firmware to version 1.0.336 or higher, and RM1800 to version 1.0.26 or higher. If updates are unavailable, consider network segmentation to limit exposure of the router management interface.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14101 — 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-14101 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