CVE-2016-5368
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 AR3200 before V200R007C00SPC900 allows remote attackers to cause a denial of service (memory consumption) via a large number of crafted Multiprotocol Label Switching (MPLS) packets.
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 confidenceA memory leak vulnerability in Huawei AR3200 routers before V200R007C00SPC900 allows remote attackers to cause denial of service by sending large numbers of crafted MPLS packets, leading to memory exhaustion on the affected device.
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= v200r005c20= v200r005c32= v200r007c00CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 modelRun 'display device' or 'display version' command on the Huawei device to confirm it is an AR3200 series routerAffected if Device is not a Huawei AR3200 model - this CVE does not apply
-
Check the firmware versionRun 'display version' to display the VRP software version. Look for version numbers v200r005c20, v200r005c32, or v200r007c00Affected if Version matches exactly one of the three affected versions listed - device is running a vulnerable release
-
Verify if MPLS is enabledRun 'display mpls interface' or 'display current-configuration | include mpls' to check if MPLS is configured on any interfaceAffected if MPLS is enabled on the device - the vulnerability can be triggered by malicious MPLS traffic
-
Check for memory exhaustion symptomsRun 'display memory usage' or 'display memory-usage' to check available memory. Compare current usage to baseline. Look for continuously increasing memory usageAffected if Memory usage is abnormally high or continuously increasing without returning to baseline, especially if MPLS traffic is being processed
A Huawei AR3200 router running firmware version v200r005c20, v200r005c32, or v200r007c00 with MPLS enabled is vulnerable to memory exhaustion when targeted with crafted MPLS packets.
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 V200R007C00SPC900 or later to the Huawei AR3200; alternatively, implement network-level filtering or ACLs to block malicious MPLS traffic at perimeter devices until the patch can be applied.
- Consultation4.0 h
- Implementation4.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5368 — 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-5368 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