CVE-2016-5822
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 · uneditedHuawei Oceanstor 5800 before V300R002C10SPC100 allows remote attackers to cause a denial of service (CPU consumption) via a large number of crafted HTTP 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 · moderate confidenceDenial of service vulnerability in Huawei Oceanstor 5800 storage systems before V300R002C10SPC100 allows remote attackers to consume CPU resources by sending large numbers of crafted HTTP packets, potentially rendering the device unavailable.
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<= v300r002c10CVSS 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 storage product modelAccess the device management interface or use the system's product information command to confirm the exact model is Huawei Oceanstor 5800 V3Affected if The model is Huawei Oceanstor 5800 V3 and the version is at or below v300r002c10
-
Determine the installed firmware versionLocate the firmware version through the device management GUI, CLI command (such as 'show version' or similar), or system information pageAffected if The firmware version is v300r002c10 or any version number lower than v300r002c10 (versions prior to V300R002C10SPC100)
-
Verify HTTP service exposureCheck the device network configuration to determine if HTTP management interface is accessible from network segments outside the trusted management networkAffected if HTTP service is enabled and reachable from untrusted network segments or the internet
-
Confirm CPU resource consumption patternMonitor device CPU utilization through the management interface or SNMP monitoring during periods of unexpected high load or during an active attackAffected if CPU utilization remains abnormally high despite normal operational load and persists after basic troubleshooting
The device is affected if it is a Huawei Oceanstor 5800 V3 running firmware version v300r002c10 or lower with HTTP interface accessible from untrusted networks.
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 dataUpgrade Huawei Oceanstor 5800 to firmware version V300R002C10SPC100 or later. Implement network segmentation and firewall rules to restrict HTTP access to trusted sources as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5822 — 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-5822 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