dbcve.org
Cloudengine 5800 FirmwareOperating system · Huawei

CVE-2016-8795

MEDIUM · 5.9 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 CloudEngine 12800 with software V100R002C00, V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00; CloudEngine 5800 with software V100R002C00, V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00; CloudEngine 6800 with software V100R002C00, V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00; CloudEngine 7800 with software V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00; CloudEngine 8800 with software V100R006C00; and Secospace USG6600 with software V500R001C00 allow remote unauthenticated attackers to craft specific IPFPM packets to trigger an integer overflow and cause the device to reset.

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

Remote unauthenticated attackers can send specially crafted IPFPM (IP Flow Performance Monitoring) packets to Huawei CloudEngine switches (12800, 5800, 6800, 7800, 8800) and Secospace USG6600 firewalls. These packets trigger an integer overflow vulnerability, causing the affected device to reset, resulting in denial of service.

MitigationApply Huawei patches for the affected software versions (V100R002C00 through V100R006C00 and V500R001C00). As an interim measure, consider filtering or rate-limiting IPFPM traffic at network perimeter points until patches can be applied.

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
Cloudengine 5800 FirmwareOperating system
Affected:= v100r002c00= v100r003c00= v100r003c10= v100r005c00= v100r005c10= v100r006c00
Cloudengine 6800 FirmwareOperating system
Affected:= v100r002c00= v100r003c00= v100r003c10= v100r005c00= v100r005c10= v100r006c00
Cloudengine 12800 FirmwareOperating system
Affected:= v100r002c00= v100r003c00= v100r003c10= v100r005c00= v100r005c10= v100r006c00
Cloudengine 7800 FirmwareOperating system
Affected:= v100r003c00= v100r003c10= v100r005c00= v100r005c10= v100r006c00
Cloudengine 8800 FirmwareOperating system
Affected:= v100r006c00
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c00

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

CVSS:3.0/AV:N/AC:H/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 device model
    Run 'display device' or 'display version' command on the Huawei device to confirm it is a CloudEngine 12800, 5800, 6800, 7800, 8800, or Secospace USG6600
    Affected if Device model is not one of these models - the CVE does not apply
  2. Check firmware version
    Run 'display version' command to retrieve the firmware version. Compare against affected versions: CloudEngine 5800/6800/12800: v100r002c00, v100r003c00, v100r003c10, v100r005c00, v100r005c10, v100r006c00; CloudEngine 7800: v100r003c00, v100r003c10, v100r005c00, v100r005c10, v100r006c00; CloudEngine 8800: v100r006c00; USG6600: v500r001c00
    Affected if Installed version matches one of the affected versions listed above
  3. Verify IPFPM feature status
    Run 'display ipfpm configuration' or check if IPFPM (IP Flow Performance Monitoring) is configured on the device. The vulnerability is triggered by specially crafted IPFPM packets, so the feature must be active for exploitation.
    Affected if IPFPM feature is enabled or configured on the device

Device is affected if it is a CloudEngine 12800/5800/6800/7800/8800 or USG6600 running one of the listed firmware versions AND the IPFPM feature is enabled, as the vulnerability requires IPFPM packets to be processed.

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 Huawei patches for the affected software versions (V100R002C00 through V100R006C00 and V500R001C00). As an interim measure, consider filtering or rate-limiting IPFPM traffic at network perimeter points until patches can be applied.

Fix this in Cloudengine 5800 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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