CVE-2016-5435
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 · uneditedMemory leak in Huawei IPS Module, NGFW Module, NIP6300, NIP6600, and Secospace USG6300, USG6500, USG6600, USG9500, and AntiDDoS8000 V500R001C00 before V500R001C20SPC100, when in hot standby networking where two devices are not directly connected, allows remote attackers to cause a denial of service (memory consumption and reboot) 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 confidenceMemory leak vulnerability in Huawei IPS, NGFW, NIP, USG, and AntiDDoS devices running V500R001C00 before V500R001C20SPC100. When configured in hot standby networking with non-directly-connected devices, remote attackers can send crafted packets to trigger memory exhaustion, causing denial of service via device reboot.
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= v5500r001c00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device model through CLI command 'display device' or via the management interface to confirm it is one of: IPS, NGFW, NIP, USG, or AntiDDoSAffected if Device is not one of these models, then not affected by this CVE
-
Check the firmware versionUse CLI command 'display version' or check the system information page to retrieve the installed firmware versionAffected if Version is V500R001C20SPC100 or later, then not affected; version is V500R001C00 or any version before V500R001C20SPC100, then potentially affected
-
Verify hot standby networking is configuredCheck the device configuration using 'display current-configuration | include hot' or access the redundancy settings in the web management interface to see if hot standby mode is enabledAffected if Hot standby networking is not configured, then not vulnerable to this specific attack vector
-
Confirm non-directly-connected device configurationReview the hot standby topology by examining 'display hrp topology' or checking the redundancy peer configuration to determine if the standby device is not directly connectedAffected if Hot standby is configured with directly-connected devices only, then likely not affected; if non-directly-connected standby devices are used, then the environment matches the vulnerable configuration
The device is affected only if it is one of the listed product models, runs firmware before V500R001C20SPC100, AND is configured with hot standby networking involving non-directly-connected devices.
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 vendor patch V500R001C20SPC100 or later to all affected devices. Until patched, monitor for abnormal memory consumption and consider network isolation of the hot standby configuration.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5435 — 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-5435 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