Ax1800 FirmwareOperating system · Mi

CVE-2020-14098

HIGH · 7.5 CVSS v3.1 Published 2021-01-13
Fix available
A fix is available. Upgrade to 1.0.26 / 1.0.336 or later.
See remediation →
84/100
Remediation priority · High
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
The login verification can be bypassed by using the problem that the time is not synchronized after the router restarts. 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 · high confidence

The Xiaomi AX1800 and RM1800 routers have an authentication bypass vulnerability where login verification can be circumvented due to improper time synchronization after a device restart. The router's login mechanism likely relies on time-based validation (e.g., for tokens or session integrity), and without synchronized system time following a reboot, the verification logic fails to function correctly, allowing unauthorized access.

MitigationUpdate the router firmware to version 1.0.336 or higher for AX1800, and version 1.0.26 or higher for RM1800 to obtain the patched firmware that ensures proper time synchronization after restarts.

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
Ax1800 FirmwareOperating system
Affected:< 1.0.336
Rm1800 FirmwareOperating system
Affected:< 1.0.26

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Check the physical device label or web interface for the exact model number (AX1800 or RM1800).
    Affected if The device is a Xiaomi AX1800 or RM1800 router.
  2. Check firmware version on AX1800
    Log into the router web interface (usually at 192.168.31.1) and navigate to Settings > Status, or use the Mi WiFi app to view the firmware version under device information.
    Affected if Running firmware version lower than 1.0.336 on the AX1800.
  3. Check firmware version on RM1800
    Log into the router web interface and navigate to Settings > Status, or use the Mi WiFi app to view the firmware version under device information.
    Affected if Running firmware version lower than 1.0.26 on the RM1800.
  4. Determine if time-based auth is in use
    Inspect the router's authentication mechanism through the web interface login process. The vulnerability specifically affects time-based token or session validation used during login.
    Affected if The router uses time-dependent verification for login sessions, which is the default authentication mechanism.
  5. Assess restart behavior
    After a router reboot, observe whether the device can be accessed without proper credentials or whether the login system fails to validate correctly due to unsynchronized system time.
    Affected if The router experiences authentication failures or allows unauthorized access immediately after a reboot before time synchronization occurs.

You are affected if you are running Xiaomi AX1800 firmware below 1.0.336 or RM1800 firmware below 1.0.26, and the router's time-based authentication can be bypassed after a restart due to unsynchronized system time.

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.

From vendor data
Upgrade available Upgrade to 1.0.26 / 1.0.336 or later
Fixed in 1.0.261.0.336
Interim mitigation

Update the router firmware to version 1.0.336 or higher for AX1800, and version 1.0.26 or higher for RM1800 to obtain the patched firmware that ensures proper time synchronization after restarts.

Fix this in Ax1800 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-14098 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14098 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