Skip to content
Fencer Intel
critical 9.1

CVE-2013-4561 json

In a openshift node, there is a cron job to update mcollective facts that mishandles a temporary file.

published 4y ago modified 4mo ago also EUVD-2013-4420

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

In a openshift node, there is a cron job to update mcollective facts that mishandles a temporary file. This may lead to loss of confidentiality and integrity.

Patch / fix

Is CVE-2013-4561 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-2013-4561 updated cvss 2.1

openshift-origin-msg-node-mcollective: /etc/cron.minutely/openshift-facts tmp file creation

  • Red Hat OpenShift Enterprise 2 openshift-origin-msg-node-mcollective
    affected: no fix available
  • Red Hat OpenShift Enterprise 1 openshift-origin-msg-node-mcollective
    not affected: vulnerable code not present

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

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1029652 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • n/a openshift-origin-msg-node-mcollective

Classification

Weakness
  • CWE-377 DEPRECATED: Insecure Temporary File
  • CWE-668 Exposure of Resource to Wrong Sphere

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.