# CVE-2016-6177: Integer overflow in OceanStor 5800 V3 V300R003C00

> An authenticated attacker can cause a denial of service in Huawei OceanStor storage arrays by sending massive abnormal NFS packets.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5m52-43pw-mf5p

## What is CVE-2016-6177?

CVE-2016-6177 is a medium-severity vulnerability in OceanStor 5800 V3 V300R003C00, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Huawei OceanStor 5800 V300R003C00 has an integer overflow vulnerability. An authenticated attacker may send massive abnormal Network File System (NFS) packets, causing an anomaly in specific disk arrays.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Huawei Oceanstor 5800 V3 Firmware.

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

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

## Is CVE-2016-6177 being exploited?

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

## Other vulnerabilities in OceanStor 5800 V3 V300R003C00

- [CVE-2017-8157](https://insights.sbomify.com/CVE-2017-8157/): OceanStor 5800 V3 with software V300R002C00 and V300R002C10, OceanStor 6900 V3 V300R001C00 has an information leakage vulnerability. (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6177 is a medium-severity vulnerability in OceanStor 5800 V3 V300R003C00, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6177 in the wild and no public exploit code.

Affected product: OceanStor 5800 V3 V300R003C00. 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-6177/ (Markdown: https://insights.sbomify.com/CVE-2016-6177/index.md)
```

## Sources

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

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