# CVE-2017-2775: Memory corruption in LabVIEW 2016 Evaluation

> A memory corruption vulnerability in LabVIEW allows remote code execution via a specially crafted VI file.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f7q2-f9g4-wwg4

## What is CVE-2017-2775?

CVE-2017-2775 is a high-severity memory corruption vulnerability in National Instruments LabVIEW 2016 Evaluation, published on 31 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An exploitable memory corruption vulnerability exists in the LvVariantUnflatten functionality in 64-bit versions of LabVIEW before 2015 SP1 f7 Patch and 2016 before f2 Patch. A specially crafted VI file can cause a user controlled value to be used as a loop terminator resulting in internal heap corruption. An attacker controlled VI file can be used to trigger this vulnerability, exploitation could lead to remote code execution.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-2775?

It affects 1 product.


Products: Ni Labview.

## How do I fix CVE-2017-2775?

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

## Is CVE-2017-2775 being exploited?

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

## Other vulnerabilities in National Instruments LabVIEW 2016 Evaluation

- [CVE-2013-5022](https://insights.sbomify.com/CVE-2013-5022/): Path traversal in n/a (critical 10.0)
- [CVE-2026-16233](https://insights.sbomify.com/CVE-2026-16233/): Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-16234](https://insights.sbomify.com/CVE-2026-16234/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-64201](https://insights.sbomify.com/CVE-2026-64201/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)
- [CVE-2026-64202](https://insights.sbomify.com/CVE-2026-64202/): Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2775 and fix it if it is affected.

What it is: CVE-2017-2775 is a high-severity memory corruption vulnerability in National Instruments LabVIEW 2016 Evaluation, published on 31 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-2775 in the wild and no public exploit code.

Affected product: National Instruments LabVIEW 2016 Evaluation. 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-2017-2775/ (Markdown: https://insights.sbomify.com/CVE-2017-2775/index.md)
```

## Sources

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

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