dbcve.org
Ar3200 FirmwareOperating system · Huawei

CVE-2016-6206

CRITICAL · 9.8 CVSS v3.0 Published 2017-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 AR3200 routers with software before V200R007C00SPC600 allow remote attackers to cause a denial of service or execute arbitrary code via a crafted packet.

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

Buffer overflow or similar memory corruption vulnerability in Huawei AR3200 routers allows remote attackers to send crafted packets and execute arbitrary code or cause denial of service. Affects firmware versions before V200R007C00SPC600.

MitigationUpgrade Huawei AR3200 firmware to V200R007C00SPC600 or later. If immediate patching is not possible, restrict network access to the router management interfaces and implement ingress filtering to block suspicious packets.

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
Ar3200 FirmwareOperating system
Affected:= v200r001c00= v200r001c01= v200r002c00= v200r002c01= v200r002c02= v200r002c05= v200r003c00= v200r003c01= v200r003c05= v200r005c00= v200r005c10= v200r005c20

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

CVSS:3.0/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 checks

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

  1. Identify the device model
    Run the command `display device` or `display version` on the router console or via remote management (SSH/Telnet). Look for the model name in the output.
    Affected if The device is not a Huawei AR3200, then this specific CVE does not apply.
  2. Retrieve the firmware version
    Run `display version` and locate the firmware version string (typically shown as V200RxxxCxx or similar). Note the complete version number including the build number if visible.
    Affected if Unable to retrieve the firmware version from the device.
  3. Compare against affected versions
    Compare the installed firmware version to the list: v200r001c00, v200r001c01, v200r002c00, v200r002c01, v200r002c02, v200r002c05, v200r003c00, v200r003c01, v200r003c05, v200r005c00, v200r005c10, v200r005c20, or any version earlier than V200R007C00SPC600.
    Affected if The installed version matches any version in the list OR is earlier than V200R007C00SPC600.

You are affected if the device is a Huawei AR3200 running firmware version V200R007C00SPC600 or earlier, specifically any version from v200r001c00 through v200r005c20.

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

Upgrade Huawei AR3200 firmware to V200R007C00SPC600 or later. If immediate patching is not possible, restrict network access to the router management interfaces and implement ingress filtering to block suspicious packets.

Recommended fix High confidence

V200R007C00SPC600 or any later release (V200R007C00SPC600+)

  1. 1. Backup the current router configuration before initiating any firmware upgrade.
  2. 2. Download the V200R007C00SPC600 or later firmware from the official Huawei support website (support.huawei.com).
  3. 3. Verify the integrity of the firmware file using the hash values provided by Huawei.
  4. 4. Access the router's web-based management interface or CLI.
  5. 5. Navigate to the firmware upgrade section (System > Device Management > Upgrade > Firmware Upgrade in web UI, or 'upgrade system' in CLI).
  6. 6. Upload the V200R007C00SPC600 or later firmware file.
  7. 7. Wait for the upgrade process to complete - do not power off the device during this process.
  8. 8. After reboot, verify the firmware version matches the intended fixed version.
Caveat Firmware upgrades may introduce compatibility changes; test in a staging environment before deploying to production, and ensure backup of configuration is available.

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

Fix this in Ar3200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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