dbcve.org
Nip6300 FirmwareOperating system · Huawei

CVE-2016-4576

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-23
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
Buffer overflow in the Application Specific Packet Filtering (ASPF) functionality in the Huawei IPS Module, NGFW Module, NIP6300, NIP6600, Secospace USG6300, USG6500, USG6600, USG9500, and AntiDDoS8000 devices with software before V500R001C20SPC100 allows remote attackers to cause a denial of service or execute arbitrary code via a crafted packet, related to "illegitimate parameters."

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

Buffer overflow in Huawei's Application Specific Packet Filtering (ASPF) allows remote attackers to execute arbitrary code or cause denial of service via crafted packets containing 'illegitimate parameters'. This critical flaw affects multiple security device models (IPS, NGFW, NIP, USG, AntiDDoS) running software versions prior to V500R001C20SPC100.

MitigationApply vendor firmware update V500R001C20SPC100 or later to affected devices. If immediate patching is not feasible, restrict network access to ASPF interfaces and implement additional ingress filtering at perimeter devices to reduce attack surface.

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
Nip6300 FirmwareOperating system
Affected:= v500r001c00
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c00
Secospace Antiddos8000 FirmwareOperating system
Affected:= v500r001c00
Usg9500 FirmwareOperating system
Affected:= v500r001c00
Secospace Usg6300 FirmwareOperating system
Affected:= v500r001c00
Ngfw Module FirmwareOperating system
Affected:= v500r001c00
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c00
Nip6600 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
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 'display version' or 'display device information' command on the Huawei device CLI
    Affected if Device is one of: Nip6300, Secospace Usg6500, Secospace Antiddos8000, Usg9500, Secospace Usg6300, Ngfw Module, Secospace Usg6600, or Nip6600
  2. Check the firmware version
    Run 'display version' and locate the software version field in the output
    Affected if Version displays as exactly v500r001c00 (any version prior to V500R001C20SPC100)
  3. Confirm ASPF feature is enabled
    Run 'display aspf status' or 'display aspf configuration' command to check if Application Specific Packet Filtering is active
    Affected if ASPF status shows as enabled or running
  4. Inspect ASPF filtering rules
    Run 'display aspf filter' or 'displayaspf policy' to view configured packet filtering rules
    Affected if ASPF contains rules that process packets and the device is processing traffic through ASPF

Device is affected if it is one of the listed Huawei models running firmware version v500r001c00 with ASPF feature enabled and processing traffic.

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

Apply vendor firmware update V500R001C20SPC100 or later to affected devices. If immediate patching is not feasible, restrict network access to ASPF interfaces and implement additional ingress filtering at perimeter devices to reduce attack surface.

Recommended fix High confidence

V500R001C20SPC100 or later

  1. 1. Back up current device configuration to ensure settings can be restored if needed.
  2. 2. Download the fixed firmware V500R001C20SPC100 (or later) from the official Huawei support website.
  3. 3. Verify the integrity of the firmware image using checksums provided by Huawei.
  4. 4. Upload the new firmware to the device via the management interface (console, SSH, or web UI).
  5. 5. Initiate the firmware upgrade process according to Huawei's standard upgrade procedure.
  6. 6. After upgrade completes, reboot the device if not automatically done.
  7. 7. Verify the device is running the new firmware version and that ASPF functionality is operational.
  8. 8. Restore configuration from backup if needed and test normal operation.

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

Fix this in Nip6300 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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