Hirouter Cd30 10 FirmwareOperating system · Huawei

CVE-2020-9122

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-12
Fix available
A fix is available. Upgrade to 10.0.2.37 / 10.0.3.33 or later.
See remediation →
70/100
Remediation priority · Elevated
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
Some Huawei products have an insufficient input verification vulnerability. Attackers can exploit this vulnerability in the LAN to cause service abnormal on affected devices.Affected product versions include:HiRouter-CD30-10 version 10.0.2.5;HiRouter-CT31-10 version 10.0.2.20;WS5200-12 version 10.0.1.9;WS5281-10 version 10.0.5.10;WS5800-10 version 10.0.3.25;WS7100-10 version 10.0.5.21;WS7200-10 version 10.0.5.21.

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 confidence

Insufficient input verification vulnerability in Huawei router firmware allowing authenticated attackers on the LAN to trigger service abnormalities through malformed input. The vulnerability affects multiple HiRouter and WS series devices.

MitigationApply vendor firmware updates when released by Huawei. Until patches are available, minimize attack surface by restricting LAN access to trusted users only and monitoring for anomalous activity.

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
Hirouter Cd30 10 FirmwareOperating system
Affected:>= 10.0.2.5, < 10.0.5.7
Hirouter Ct31 10 FirmwareOperating system
Affected:>= 10.0.2.20, < 10.0.2.37
Ws5200 12 FirmwareOperating system
Affected:>= 10.0.1.9, <= 10.0.5.6
Ws5281 10 FirmwareOperating system
Affected:>= 10.0.5.10, < 10.0.5.32
Ws5800 10 FirmwareOperating system
Affected:>= 10.0.3.25, < 10.0.3.33
Ws7100 10 FirmwareOperating system
Affected:>= 10.0.5.21, < 10.0.5.37
Ws7200 10 FirmwareOperating system
Affected:>= 10.0.5.21, < 10.0.5.37

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device model
    Check the device label, web admin interface, or SSH into the device to determine the exact model (HiRouter CD30, HiRouter CT31, WS5200, WS5281, WS5800, WS7100, or WS7200)
    Affected if Device is one of the seven affected models listed in the CVE
  2. Locate the firmware version
    Access the device web admin panel (typically at 192.168.1.1) and navigate to System Settings > Firmware Version, or check via SSH using 'version' or 'cat /proc/version' commands
    Affected if Unable to retrieve firmware version information
  3. Compare firmware version against affected ranges
    Match your installed firmware version to these ranges: CD30 >= 10.0.2.5 and < 10.0.5.7; CT31 >= 10.0.2.20 and < 10.0.2.37; WS5200 >= 10.0.1.9 and <= 10.0.5.6; WS5281 >= 10.0.5.10 and < 10.0.5.32; WS5800 >= 10.0.3.25 and < 10.0.3.33; WS7100 >= 10.0.5.21 and < 10.0.5.37; WS7200 >= 10.0.5.21 and < 10.0.5.37
    Affected if Your installed version falls within any of the specified version ranges for your model
  4. Verify LAN admin access is enabled
    Check the device web interface under LAN settings or Administration to confirm whether remote/LAN management is enabled, which would allow authenticated users on the local network to access admin functions
    Affected if LAN management interface is exposed and accessible to untrusted users on the local network

Your device is affected if it is one of the seven listed models AND its firmware version falls within the specified version ranges AND the LAN admin interface is accessible to authenticated 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.

From vendor data
Upgrade available Upgrade to 10.0.2.37 / 10.0.3.33 / 10.0.5.7 or later
Fixed in 10.0.2.3710.0.3.3310.0.5.7
Interim mitigation

Apply vendor firmware updates when released by Huawei. Until patches are available, minimize attack surface by restricting LAN access to trusted users only and monitoring for anomalous activity.

Fix this in Hirouter Cd30 10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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