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

> Remote authenticated users can cause a denial of service in NetApp Data ONTAP via unsafe user input string handling.

- **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 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-488x-jpc9-9c55

## What is CVE-2016-1895?

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

### Official description

NetApp Data ONTAP before 8.2.5 and 8.3.x before 8.3.2P12 allow remote authenticated users to cause a denial of service via vectors related to unsafe user input string handling.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Netapp Data Ontap.

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

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

## Is CVE-2016-1895 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3349](https://insights.sbomify.com/CVE-2008-3349/): Auth bypass in n/a (critical 10.0)
- [CVE-2015-7746](https://insights.sbomify.com/CVE-2015-7746/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-5502](https://insights.sbomify.com/CVE-2019-5502/): Weak cryptography in Data ONTAP operating in 7-Mode (critical 9.1)
- [CVE-2016-5374](https://insights.sbomify.com/CVE-2016-5374/): Missing authorization in n/a (high 8.8)
- [CVE-2015-8322](https://insights.sbomify.com/CVE-2015-8322/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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