# CVE-2016-5047: Denial of service in n/a

> Remote authenticated users can cause a denial of service in NetApp OnCommand System Manager, requiring an upgrade to mitigate.

- **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:** 1 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mg54-7h26-f533

## What is CVE-2016-5047?

CVE-2016-5047 is a medium-severity denial of service vulnerability in n/a, published on 1 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NetApp OnCommand System Manager 8.3.x before 8.3.2P5 allows remote authenticated users to cause a denial of service via unspecified vectors.

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

It affects 1 product.


Products: Netapp Oncommand System Manager.

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

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

## Is CVE-2016-5047 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-5045](https://insights.sbomify.com/CVE-2016-5045/): Information disclosure in n/a (high 8.1)
- [CVE-2013-3321](https://insights.sbomify.com/CVE-2013-3321/): Path traversal in n/a (high 7.5)
- [CVE-2016-3063](https://insights.sbomify.com/CVE-2016-3063/): Code injection in n/a (high 7.5)
- [CVE-2013-3322](https://insights.sbomify.com/CVE-2013-3322/): Command injection in n/a (high 7.2)
- [CVE-2013-3320](https://insights.sbomify.com/CVE-2013-3320/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5047 is a medium-severity denial of service vulnerability in n/a, published on 1 Sep 2016. 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-5047 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-5047/ (Markdown: https://insights.sbomify.com/CVE-2016-5047/index.md)
```

## Sources

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

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