Skip to content
Fencer Intel
high 7.5

CVE-2017-1000198 json

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…

published 8y ago modified 4mo ago also EUVD-2017-1475

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 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

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

  • tcmu-runner SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 1.0.4-3.3.10

suse advisories SUSE-SU-2017:2601-1

Is CVE-2017-1000198 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-1000198 updated cvss 5.5

tcmu-runner: glfs handler allows local DoS via crafted CheckConfig strings

  • 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

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

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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.