Skip to content
Fencer Intel
low 2.1

CVE-2014-0164 json

openshift-origin-broker-util, as used in Red Hat OpenShift Enterprise 1.2.7 and 2.0.5, uses world-readable permissions for the mcollective…

published 2014-05-05 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0219

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

openshift-origin-broker-util, as used in Red Hat OpenShift Enterprise 1.2.7 and 2.0.5, uses world-readable permissions for the mcollective client.cfg configuration file, which allows local users to obtain credentials and other sensitive information by reading the file.

Patch / fix

  • mcollective Debian 12 1.2.1+dfsg-2

debian advisories DEBIAN-CVE-2014-0164

  • openshift-origin-broker-util openshift 1.2 1.9.16-1.el6op
  • openshift-origin-broker-util openshift 2.0 1.17.6.6-1.el6op

red hat advisories RHSA-2014:0461RHSA-2014:0460

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-2014-0164 updated cvss 4.6

mcollective: world readable client config

  • Red Hat OpenShift Enterprise 1 mcollective Red Hat OpenShift Enterprise 2 ruby193-mcollective
    affected: no fix available
  • Red Hat RHOSE Infrastructure 1.2 openshift-origin-broker-util 1.9.16-1.el6op
    fixed: vendor fix RHSA-2014:0461
  • Red Hat RHOSE Infrastructure 2.0 openshift-origin-broker-util 1.17.6.6-1.el6op
    fixed: vendor fix RHSA-2014:0460

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.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

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.