PyMoDAQ code execution in crafted file handling
PyMoDAQ · pymodaq_data · pymodaq_gui · pymodaq_utils
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| PyMoDAQ PyMoDAQ |
| No fix yet |
| PyMoDAQ pymodaq_data |
| No fix yet |
| PyMoDAQ pymodaq_gui |
|
PyMoDAQ · pymodaq_data · pymodaq_gui · pymodaq_utils
| Product | Affected | Fixed in |
|---|---|---|
| PyMoDAQ PyMoDAQ |
| No fix yet |
| PyMoDAQ pymodaq_data |
| No fix yet |
| PyMoDAQ pymodaq_gui |
|
≥ 5.3.0 · < 5.3.10| No fix yet |
| PyMoDAQ pymodaq_utils |
| No fix yet |
PyMoDAQ before 4.4.13, and pymodaq_data, pymodaq_gui, and pymodaq_utils before 5.1.15, 5.2.x before 5.2.14, and 5.3.x before 5.3.10, contain deserialization of untrusted data and eval injection vulnerabilities that allow attackers to execute arbitrary code by supplying crafted files that a user opens. Attackers can store pickled objects in HDF5 string nodes that StringARRAY.array_to_string() passes to pickle.loads() when the node is browsed or read, place Python expressions in HDF5 attributes that JsonConverter.json2object() evaluates, supply a .dock file that load_layout_state() unpickles from the Dashboard Load layout action, or embed Python expressions in XML settings files that elt_to_dict() and set_txt_from_elt() evaluate.
From the CVE record · VulnCheck
PyMoDAQ and its data, GUI, and utils packages deserialize untrusted data or evaluate expressions in HDF5, layout, and XML settings files. An attacker can execute arbitrary code by supplying a crafted file that a user opens.
Check installations of PyMoDAQ before 4.4.13 and pymodaq_data, pymodaq_gui, or pymodaq_utils before 5.1.15, in the 5.2.x series before 5.2.14, or in the 5.3.x series before 5.3.10.