dbcve.org
Ax9000 FirmwareOperating system · Mi

CVE-2024-45348

HIGH · 8.8 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to 1.0.174 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Xiaomi Router AX9000 has a post-authorization command injection vulnerability. This vulnerability is caused by the lack of validation of user input, and an attacker can exploit this vulnerability to execute arbitrary 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 · high confidence

The Xiaomi Router AX9000 contains a post-authentication command injection vulnerability where insufficient input validation allows authenticated attackers to inject and execute arbitrary commands on the underlying operating system. This enables complete compromise of the router's firmware and connected network.

MitigationApply the vendor firmware update when available. Until then, restrict administrative interface access to trusted IP addresses/networks and use strong, unique credentials to reduce the attack surface.

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
Ax9000 FirmwareOperating system
Affected:< 1.0.174

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

CVSS:3.1/AV:N/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 checks

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

  1. Identify the router model
    Log into the router web interface (typically http://192.168.1.1) and check the device status page or go to Settings > System > Status to confirm the model is 'AX9000' or 'Mi AX9000'
    Affected if The device is not a Xiaomi AX9000 model
  2. Check the installed firmware version
    In the router web interface, navigate to Settings > System > Firmware Version or Status page and note the exact firmware version number displayed
    Affected if The firmware version is lower than 1.0.174 (for example, 1.0.172, 1.0.173, or any version starting with 1.0.x below 174)
  3. Verify remote management is enabled
    In the router web interface, go to Settings > Security > Remote Access or Settings > Administration and check if 'Remote Management' or 'Allow remote access from WAN' is enabled
    Affected if Remote administrative access from WAN is enabled, exposing the login page to the internet
  4. Confirm administrative interface accessibility
    Attempt to access the router admin page from outside the local network (or check router firewall settings) to determine if the login page is reachable from untrusted networks
    Affected if The administrative interface is directly accessible from the internet without VPN or IP restriction

The device is affected if it is a Xiaomi AX9000 running firmware version below 1.0.174 and the administrative interface is accessible to an attacker (locally or remotely) who could supply malicious commands after authenticating.

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.174 or later
Fixed in 1.0.174
Interim mitigation

Apply the vendor firmware update when available. Until then, restrict administrative interface access to trusted IP addresses/networks and use strong, unique credentials to reduce the attack surface.

Recommended fix Moderate confidence

Xiaomi Router AX9000 Firmware 1.0.174 or later

  1. Download the Xiaomi Router AX9000 firmware version 1.0.174 or later from the official Xiaomi support site (trust.mi.com or mi.com)
  2. Access the router web management interface at the default IP (typically 192.168.31.1)
  3. Navigate to the firmware upgrade or system settings section
  4. Upload the downloaded firmware file and initiate the upgrade process
  5. Wait for the router to complete the upgrade and reboot automatically
  6. After reboot, verify the firmware version has been updated to 1.0.174 or later in the system settings
Caveat Router firmware upgrades typically require a brief downtime; ensure configuration backups before upgrading

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

Fix this in Ax9000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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