CVE-2017-2779
CVE-2017-2779 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, talos
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
2%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
References
4 on the record
- www.securityfocus.com/bid/100519
vdb-entry, x_refsource_BID
- 0patch.blogspot.com/2017/09/0patching-rsrc-arbitrary-null-write.html
x_refsource_MISC
- www.talosintelligence.com/vulnerability_reports/TALOS-2017-0273
x_refsource_MISC
- www.ni.com/product-documentation/54099/en/
x_refsource_CONFIRM
Elsewhere on this site
- national instrumentsevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.