Tcmu Runner Project maintains a niche but strategically positioned userspace framework for managing SCSI target emulation in Linux environments, where the narrow product scope belies its presence in storage-infrastructure deployments. The vulnerability surface reflects the complexity of SCSI protocol handling and target-mode I/O operations; current severity, exploitation, and exposure figures are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Tcmu Runner Project over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-3139HIGH In Open-iSCSI tcmu-runner 1.3.x, 1.4.x, and 1.5.x through 1.5.2, xcopy_locate_udev in tcmur_cmd_handler.c lacks a check for transport-layer restrictions, allowing remote attackers | Jan 13, 2021 | 8.1 | 25 | NO | NO |
CVE-2017-1000200HIGH tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a dbus triggered NULL pointer dereference in the tcmu-runner daemon's on_unregister_handler() function resulting in denial of se | Nov 17, 2017 | 7.5 | 23 | NO | NO |
CVE-2017-1000199HIGH tcmu-runner version 0.91 up to 1.20 is vulnerable to information disclosure in handler_qcow.so resulting in non-privileged users being able to check for existence of any file with | Nov 17, 2017 | 7.5 | 23 | NO | NO |
CVE-2017-1000198HIGH tcmu-runner daemon version 0.9.0 to 1.2.0 is vulnerable to invalid memory references in the handler_glfs.so handler resulting in denial of service | Nov 17, 2017 | 7.5 | 23 | NO | NO |
CVE-2017-1000201MEDIUM The tcmu-runner daemon in tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a local denial of service attack | Nov 17, 2017 | 5.5 | 19 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Tcmu Runner Project.
Media articles that mention a CVE ID that affects a product developed by Tcmu Runner Project — matched by CVE ID, not by vendor name.