CVE-2020-14124
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 · uneditedThere is a buffer overflow in librsa.so called by getwifipwdurl interface, resulting in code execution on Xiaomi router AX3600 with ROM version =rom< 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 · moderate confidenceA buffer overflow vulnerability exists in the librsa.so library within the getwifipwdurl interface on Xiaomi AX3600 routers running firmware versions prior to 1.1.12. The flaw allows remote attackers to achieve code execution due to insufficient bounds checking when processing input, potentially enabling complete router compromise.
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.1.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Xiaomi AX3600Log into the router admin panel or check the device label to verify the model number is Mi AX3600Affected if Device is not a Xiaomi AX3600 router - different models are not affected by this specific CVE
-
Check installed firmware versionAccess router admin interface (typically at 192.168.31.1), navigate to Status or System Settings, and locate the firmware version displayed there. Alternatively, check via CLI if SSH access is enabled using 'cat /proc/xiaoqiang/board_info' or similar commandAffected if Firmware version is 1.1.12 or lower, indicating the router is running a vulnerable version
-
Verify librsa.so library presenceIf SSH/telnet access is available, check for the librsa.so library file existence - typically located in /lib or /usr/lib directories on the router filesystemAffected if The librsa.so library exists on the device, which is required for the vulnerable code path to be present
-
Identify getwifipwdurl interface accessibilityReview router network services and HTTP endpoints. This interface is typically an internal API. Check if the router's web interface or API endpoints expose this function - this may require examining the HTTP requests the router makes or reverse engineering the firmwareAffected if The getwifipwdurl interface is exposed and accessible on the network, making remote exploitation possible
A Xiaomi AX3600 router running firmware version 1.1.12 or lower is affected by this vulnerability if the librsa.so library with the vulnerable getwifipwdurl interface is present and accessible on the 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.
dbcve · scopedUpgrade Xiaomi AX3600 router firmware to version 1.1.12 or later to remediate the buffer overflow in librsa.so. If immediate patching is not feasible, restrict network access to the vulnerable interface and monitor for indicators of compromise.
Xiaomi AX3600 firmware version > 1.1.12 (latest stable release)
- 1. Access the Xiaomi AX3600 router management interface via web browser (typically at 192.168.31.1)
- 2. Navigate to the firmware settings or system update section
- 3. Check the current firmware version under router status or system information
- 4. If the current version is 1.1.12 or earlier, initiate a firmware update to obtain the latest stable release
- 5. Alternatively, download the latest firmware from Xiaomi's official support website for the AX3600 model
- 6. Upload the firmware file through the router's web interface or use the Mi WiFi app for update
- 7. Wait for the update process to complete - do not power off the router during this process
- 8. After reboot, verify the new firmware version is installed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14124 — 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-14124 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