CVE-2017-1000200 json
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_han…
published 2017-11-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1477
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
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 service
Patch / fix
- 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
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-1000200 updated cvss 5.5
tcmu-runner: UnregisterHandler D-Bus method in tcmu-runner daemon for internal handler causes DoS
-
Red Hat Ceph Storage 2 libtcmu, tcmu-runneraffected: 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.el7rhgsfixed: 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
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/open-iscsi/tcmu-runner/pull/200/commits/bb80e9c7a798f035768260ebdadffb6eb0786178
patch, third-party-advisory
-
access.redhat.com
/errata/RHSA-2017:3277
vendor-advisory
Sources
- CVE List CVE-2017-1000200
- NVD CVE-2017-1000200
Fencer Vulns 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.