CVE-2016-5722
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 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18800 V3, and 18500 V3 before V300R003C10 sends the plaintext session token in the HTTP header, which allows remote attackers to conduct replay attacks and obtain sensitive information by sniffing the network.
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 OceanStor V3 storage systems transmit session authentication tokens in cleartext HTTP headers before V300R003C10, allowing network eavesdroppers to capture valid session tokens and reuse them in replay attacks to impersonate legitimate users and access sensitive data.
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<= v300r003c00spc100<= v300r002c10spc200CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 OceanStor V3 systemLog into the storage system management interface or check the product model via 'show system' command in CLI. Confirm the model is OceanStor V3 series.Affected if System is not OceanStor V3 product line
-
Check firmware versionIn the management GUI, navigate to System > Maintenance > Upgrade, or run 'show version' in CLI. Note the exact firmware version string (e.g., v300r003c00spc100).Affected if Firmware version is v300r003c00spc100 or earlier, OR v300r002c10spc200 or earlier
-
Verify HTTP management is enabledIn the management interface, go to Settings > Network > Service Settings. Check if HTTP (port 80) is enabled for the DeviceManager or CLI management access.Affected if HTTP is enabled and used for management access (HTTPS is not enforced)
-
Inspect network traffic for cleartext tokensCapture packets on the management network using tcpdump or Wireshark. Filter for HTTP traffic to the device manager port. Look for headers containing session tokens, JSESSIONID, or auth cookies transmitted over unencrypted connections.Affected if Authentication tokens are visible in cleartext HTTP headers in captured traffic
A user is affected if they run an OceanStor V3 system with firmware <= v300r003c00spc100 or <= v300r002c10spc200 AND have HTTP management enabled, with tokens observable in cleartext network traffic.
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 OceanStor V3 systems to firmware version V300R003C10 or later, which implements encrypted token transmission. Until upgraded, network segmentation and monitoring for unauthorized header access are recommended.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5722 — 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-5722 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