dbcve.org
Ar1200 FirmwareOperating system · Huawei

CVE-2018-7920

HIGH · 7.5 CVSS v3.0 Published 2018-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Huawei AR1200 V200R006C10SPC300, AR160 V200R006C10SPC300, AR200 V200R006C10SPC300, AR2200 V200R006C10SPC300, AR3200 V200R006C10SPC300 devices have an improper resource management vulnerability. Due to the improper implementation of ACL mechanism, a remote attacker may send TCP messages to the management interface of the affected device to exploit this vulnerability. Successful exploit could exhaust the socket resource of management interface, leading to a DoS condition.

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

Improper ACL (Access Control List) mechanism implementation in Huawei AR1200, AR160, AR200, AR2200, and AR3200 routers running V200R006C10SPC300 allows unauthenticated remote attackers to send TCP messages to the management interface, exhausting socket resources and causing denial of service.

MitigationApply vendor patch when available; restrict management interface access via network-level filtering or ACLs on upstream devices; implement rate limiting on management plane interfaces.

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
Ar1200 FirmwareOperating system
Affected:= v200r006c10spc300
Ar160 FirmwareOperating system
Affected:= v200r006c10spc300
Ar200 FirmwareOperating system
Affected:= v200r006c10spc300
Ar2200 FirmwareOperating system
Affected:= v200r006c10spc300
Ar3200 FirmwareOperating system
Affected:= v200r006c10spc300

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

CVSS:3.0/AV:N/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 router model
    Run the command 'display device' or 'display version' in the system view to confirm the hardware model is one of: AR1200, AR160, AR200, AR2200, or AR3200
    Affected if The model is any of the listed affected series
  2. Check the firmware version
    Run the command 'display version' and locate the VRP (Versatile Routing Platform) version string. Confirm it matches exactly: v200r006c10spc300
    Affected if The firmware version is exactly v200r006c10spc300
  3. Verify management interface status
    Run 'display ip interface' or 'display interface' for the management interface (typically GigabitEthernet0/0/0 or similar) to confirm it is administratively up and has an IP address configured
    Affected if A management interface is configured and active on the device
  4. Check ACL configuration on management interface
    Run 'display acl all' or examine the ACL applied to the management interface using 'display current-configuration interface [management-interface]'
    Affected if No ACL is applied to the management interface, or the ACL permits unrestricted TCP access from untrusted sources

You are affected if your router is an AR1200/AR160/AR200/AR2200/AR3200 model running firmware version v200r006c10spc300 and the management interface is accessible without restrictive ACLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; restrict management interface access via network-level filtering or ACLs on upstream devices; implement rate limiting on management plane interfaces.

Fix this in Ar1200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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