Security readout for executives and security teams
CVE-2017-2779 is a LabVIEW file-parsing flaw. A malicious Virtual Instrument file could corrupt memory when opened, potentially allowing code execution. The main business risk is compromise of engineering or operational workstations that handle LabVIEW files, especially where users exchange project files externally. Exposure is most likely where National Instruments LabVIEW 2014, 2015, 2016, or 2017 is installed and users open VI files from email, shared drives, vendors, or partners. The structured affected record specifically lists LabVIEW 2016 version 16.0, while the description names additional releases. Treat this as a targeted workstation risk rather than a broad internet-facing emergency. Prioritize engineering environments, labs, and operational teams using older LabVIEW versions, because successful exploitation could affect sensitive designs, instrumentation workflows, or system integrity. Mitigation focus: Check NI advisory 54099 for official remediation and supported version guidance.; Restrict opening VI files from untrusted external sources.; Inventory LabVIEW 2014 through 2017 installations on engineering systems..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-2779 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.5HighVector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://0patch.blogspot.com/2017/09/0patching-rsrc-arbitrary-null-write.htmlCVE reference · x_refsource_MISC
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0273CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.