# CVE-2016-0917: Auth bypass in n/a

> Remote attackers can execute arbitrary code or read/write files by exploiting duplicate NTLM nonces in the SMB service of EMC VNX storage systems.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8g56-72qr-4pmv

## What is CVE-2016-0917?

CVE-2016-0917 is a critical authentication bypass vulnerability in n/a, published on 21 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SMB service in EMC VNXe (VNXe3200 Operating Environment prior to 3.1.5.8711957 and VNXe3100/3150/3300 Operating Environment prior to 2.4.4.22638), VNX1 File OE before 7.1.80.3, VNX2 File OE before 8.1.9.155, and Celerra (all supported versions) does not prevent duplicate NTLM challenge-response nonces, which makes it easier for remote attackers to execute arbitrary code, or read or write to files, via a series of authentication requests, a related issue to CVE-2010-0231.

Weakness: CWE-264

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

It affects 3 products.


Products: Emc Vnx1 Oe Firmware, Emc Vnx2 Oe Firmware, Emc Vnxe Oe Firmware.

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

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

## Is CVE-2016-0917 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-0917 is a critical authentication bypass vulnerability in n/a, published on 21 Sep 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-0917 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-0917/ (Markdown: https://insights.sbomify.com/CVE-2016-0917/index.md)
```

## Sources

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

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