CVE-2016-8802
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 · uneditedThe security policy processing module in Huawei Secospace USG6300 with software V500R001C20SPC100, V500R001C20SPC101, V500R001C20SPC200; Secospace USG6500 with software V500R001C20SPC100, V500R001C20SPC101, V500R001C20SPC200; Secospace USG6600 with software V500R001C20SPC100, V500R001C20SPC101, V500R001C20SPC200 allows authenticated attackers to setup a specific security policy into the devices, causing a buffer overflow and crashing the system.
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 confidenceThe security policy processing module in Huawei Secospace USG6300, USG6500, and USG6600 firewall appliances contains a buffer overflow vulnerability. An authenticated attacker can craft a specific security policy that triggers the overflow, causing the system to crash. This is a denial-of-service vulnerability requiring valid authentication credentials.
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= v500r001c20spc100= v500r001c20spc101= v500r001c20spc200= v500r001c20spc100= v500r001c20spc101= v500r001c20spc200= v500r001c20spc100= v500r001c20spc101= v500r001c20spc200CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the firewall CLI or web interface and run 'display device' or check the system information page to confirm the model is USG6300, USG6500, or USG6600Affected if Device is not one of these three models
-
Check firmware versionRun 'display version' in the CLI or check the firmware version in the web interface under System > Maintenance > VersionAffected if Version is v500r001c20spc100, v500r001c20spc101, or v500r001c20spc200
-
Verify management access is enabledCheck the device network configuration for active management interfaces (HTTP, HTTPS, SSH, TELNET) by running 'display ip interface' or reviewing the interface bindingsAffected if Management interfaces are listening and accessible from untrusted networks
-
Confirm security policy module is activeRun 'display security policy all' or check via the web interface under Policy > Security Policy to see if any security policies are configuredAffected if Security policies can be created or modified by authenticated users
Device is affected if it is a USG6300/6500/6600 running firmware version v500r001c20spc100, v500r001c20spc101, or v500r001c20spc200 and has management access available for authenticated users to configure security policies
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied firmware patch or upgrade to a patched software version. Restrict management interface access to trusted IP addresses to reduce the attack surface until the patch can be applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8802 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-8802 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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