The tcmu-runner daemon in tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a local denial of service attack

published 2017-11-17 8y ago modified 2026-06-17 4mo ago also EUVD-2017-1478

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits: 0; none known

Patch / fix

distros 1 links 1

tcmu-runner storage 3.3 1.2.0-16.el7rhgs
libtcmu storage 3.3 1.2.0-16.el7rhgs

red hat advisories RHSA-2017:3277

github.com/open-iscsi/tcmu-runner#200 commit

Is CVE-2017-1000201 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000201 updated 2026-05-13 cvss 5.5

tcmu-runner: UnregisterHandler dbus method in tcmu-runner daemon for non-existing handler causes DoS

Red Hat Ceph Storage 2 libtcmu, tcmu-runner
affected: no fix available
Red Hat Gluster Storage Server 3.3 on RHEL-7 libtcmu 1.2.0-16.el7rhgs, tcmu-runner 1.2.0-16.el7rhgs
fixed: vendor fix RHSA-2017:3277

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-20 Improper Input Validation

References

github.com /open-iscsi/tcmu-runner/pull/200/commits/e2d953050766ac538615a811c64b34358614edce
patch, third-party-advisory
access.redhat.com /errata/RHSA-2017:3277
vendor-advisory

Sources

CVE List CVE-2017-1000201
NVD CVE-2017-1000201

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.