CVE-2017-2779
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/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
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
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2779?
How severe is CVE-2017-2779?
How do I fix CVE-2017-2779?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2773An issue was discovered in Pivotal PCF Elastic Runtime 1.6.x…
- CVE-2017-2774Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-2775An exploitable memory corruption vulnerability exists in the…7.5
- CVE-2017-2776Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-2777An exploitable heap overflow vulnerability exists in the ipS…8.8
- CVE-2017-2778Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-2780An exploitable heap buffer overflow vulnerability exists in …9.8
- CVE-2017-2781An exploitable heap buffer overflow vulnerability exists in …9.8
- CVE-2017-2782An integer overflow vulnerability exists in the X509 certifi…6.5
- CVE-2017-2783An exploitable heap corruption vulnerability exists in the F…8.3
- CVE-2017-2784An exploitable free of a stack pointer vulnerability exists …8.1
- CVE-2017-2785An exploitable buffer overflow exists in the psnotifyd appli…10
Are you affected by CVE-2017-2779?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
