CVE-2017-2779 Memory corruption in LabVIEW 2016
A memory corruption vulnerability in LabVIEW allows attackers to execute arbitrary code via a specially crafted Virtual Instrument file.
- 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
- None listed
What is CVE-2017-2779?
CVE-2017-2779 is a high-severity memory corruption vulnerability in National Instruments LabVIEW 2016, published on 5 Sep 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 RSRC segment parsing functionality of LabVIEW 2017, LabVIEW 2016, LabVIEW 2015, and LabVIEW 2014. A specially crafted Virtual Instrument (VI) file can cause an attacker controlled looping condition resulting in an arbitrary null write. An attacker controlled VI file can be used to trigger this vulnerability and can potentially result in code execution.
Weakness: CWE-787
Which versions are affected by CVE-2017-2779?
It affects 1 product.
Products include Ni Labview.
How do I fix CVE-2017-2779?
No fix has been published for CVE-2017-2779 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-2779 being exploited?
There is no known exploitation of CVE-2017-2779 in the wild and no public exploit code.
Other vulnerabilities in National Instruments LabVIEW 2016
- CVE-2013-5022 Path traversal in n/a
- CVE-2026-16233 Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI
- CVE-2026-16234 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI
- CVE-2026-64201 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI
- CVE-2026-64202 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI
Sources
Also known as GHSA-53vp-wxjp-8gw8.