CVE-2017-2779

HIGHCVSS 7.5/10EPSS 2.17%

Last modified

CVE-2017-2779 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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

CVSS 3.0
7.5/10

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Probability
2.17%

80.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
NiLabview2014
NiLabview2015
NiLabview2016
NiLabview2017

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-2779?
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.
How severe is CVE-2017-2779?
CVE-2017-2779 has a CVSS score of 7.5/10 (HIGH severity). 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.

How Strix Helps

Related CVEs from 2017

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