# CVE-2016-5722: Information disclosure in n/a

> Remote attackers can sniff network traffic to steal plaintext session tokens, enabling replay attacks and unauthorized access to Huawei OceanStor storage systems.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wxj5-3w49-r522

## What is CVE-2016-5722?

CVE-2016-5722 is a high-severity vulnerability in n/a, published on 24 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-5722?

It affects 1 product.


Products: Huawei Ocean Stor Firmware.

## How do I fix CVE-2016-5722?

No fix has been published for CVE-2016-5722 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-5722 being exploited?

There is no known exploitation of CVE-2016-5722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5722 and fix it if it is affected.

What it is: CVE-2016-5722 is a high-severity vulnerability in n/a, published on 24 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5722 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-5722/ (Markdown: https://insights.sbomify.com/CVE-2016-5722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-5722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-5722
- OSV: https://osv.dev/vulnerability/CVE-2016-5722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-5722/
Summaries are generated and may contain mistakes; the official description above is the record.