Ni National Instruments

Absolute path traversal vulnerability in the 3D Graph ActiveX control in cw3dgrph.ocx in National Instruments LabWindows/CVI 2012 SP1 and earlier, LabVIEW 2012 SP1 and earlier, and other products allows remote attackers to create and execute arbitrary files via a full pathname in an argument to the ExportStyle method, in conjunction with file content in the (1) Caption or (2) FormatString property value.

Multiple absolute path traversal vulnerabilities in National Instruments cwui.ocx, as used in National Instruments LabWindows/CVI 2012 SP1 and earlier, National Instruments LabVIEW 2012 SP1 and earlier, the Data Analysis component in ABB DataManager 1 through 6.3.6, and other products allow remote attackers to create and execute arbitrary files via a full pathname in an argument to the ExportStyle method in the (1) CWNumEdit, (2) CWGraph, (3) CWBoolean, (4) CWSlide, or (5) CWKnob ActiveX control, in conjunction with file content in the (a) Caption or (b) FormatString property value.

Missing input check in lvpict.cpp used in NI LabVIEW

Code Injection Vulnerability in NI LabVIEW when using CIN nodes

Memory Corruption Issue in NI LabVIEW due to improper error handling

Out of Bounds Write Vulnerability in NI LabVIEW reading CPU info from cache

Out of Bounds Write Vulnerability in NI LabVIEW in InitCPUInformation()

Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI

Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI

Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI

Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI

Out-of-Bounds Write Vulnerability in NI LabVIEW when loading lvlib file

Out-of-Bounds Write Vulnerability in NI LabVIEW when loading lvclass file

Out-of-Bounds Read in sentry_transaction_context_set_operation()

Out-of-Bounds Write in ResFileFactory::InitResourceMgr()

Out-of-Bounds Read in mgcore_SH_25_3!aligned_free()

Stack-based Buffer Overflow in LVResource::DetachResource() in NI LabVIEW

Out-of-Bounds Read in LVResFile::RGetMemFileHandle() in NI LabVIEW

Out of Bounds Write in mgocre_SH_25_3!RevBL() in NI LabVIEW

Out-of-Bounds Read in lvre!DataSizeTDR() in NI LabVIEW

Out-of-Bounds Read in lvre!ExecPostedProcRecPost() in NI LabVIEW

Out-of-Bounds Read in LVResource::DetachResource() in NI LabVIEW

Out-of-Bounds Read in lvre!VisaWriteFromFile() in NI LabVIEW

Out-of-Bounds Read in LVResFile::FindRsrcListEntry() in NI LabVIEW

Use-after-Free in sentry!sentry_span_set_data() in NI LabVIEW

Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI

Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI

Memory Corruption Due to Improper Length Checks in LabVIEW tdcore.dll

Memory Corruption Due to Improper Length Check in NI LabVIEW

Out of bounds read in HeapObjMapImpl.cpp in NI LabVIEW

Out of bounds read when loading the font table in fontmgr.cpp in NI LabVIEW

Out of bounds read in BuildFontMap in fontmgr.cpp in NI LabVIEW

An exploitable memory corruption vulnerability exists in the LvVariantUnflatten functionality in 64-bit versions of LabVIEW before 2015 SP1 f7 Patch and 2016 before f2 Patch. A specially crafted VI file can cause a user controlled value to be used as a loop terminator resulting in internal heap corruption. An attacker controlled VI file can be used to trigger this vulnerability, exploitation could lead to remote code execution.

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.

Out of Bounds Write Due to Missing Bounds Check in LabVIEW

Improper Error Handling Issue in LabVIEW

Improper Error Handling Issue in LabVIEW

Out of Bounds Write Due to Missing Bounds Check in LabVIEW

Out of Bounds Write Due to Missing Bounds Check in LabVIEW

Out of Bounds Read Due to Missing Bounds Check in LabVIEW