CVE-2017-2779

Name: CVE-2017-2779
Creator: NVD / NIST
Published: 2017-09-05T18:29:00.257+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.17%

Last modified Jun 17, 2026

CVE-2017-2779 is a vulnerability of currently unknown severity. 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. EPSS estimates a 2.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

2.17%

80.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-787

Affected Software

Vendor	Product	Versions
Ni	Labview	2014
Ni	Labview	2015
Ni	Labview	2016
Ni	Labview	2017

References

http://www.ni.com/product-documentation/54099/en/Mitigation, Vendor Advisory
http://www.securityfocus.com/bid/100519Third Party Advisory, VDB Entry
https://0patch.blogspot.com/2017/09/0patching-rsrc-arbitrary-null-write.htmlExploit, Patch, Third Party Advisory
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0273Exploit, Third Party Advisory, VDB Entry
http://www.ni.com/product-documentation/54099/en/Mitigation, Vendor Advisory
http://www.securityfocus.com/bid/100519Third Party Advisory, VDB Entry
https://0patch.blogspot.com/2017/09/0patching-rsrc-arbitrary-null-write.htmlExploit, Patch, Third Party Advisory
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0273Exploit, Third Party Advisory, VDB Entry

Timeline

Published: Sep 5, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-2779?

How severe is CVE-2017-2779?

Severity scoring for CVE-2017-2779 is pending analysis. The EPSS model estimates a 2.17% probability of exploitation in the next 30 days.

How do I fix CVE-2017-2779?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-2779?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST