Skip to content
Fencer Intel
medium 6.3

CVE-2013-4214 json

rss-newsfeed.php in Nagios Core 3.4.4, 3.5.1, and earlier, when MAGPIE_CACHE_ON is set to 1, allows local users to overwrite arbitrary file…

published 12y ago modified 4mo ago also EUVD-2013-4119

cvss
6.3
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 29%
public exploits
0
none known

Summary

rss-newsfeed.php in Nagios Core 3.4.4, 3.5.1, and earlier, when MAGPIE_CACHE_ON is set to 1, allows local users to overwrite arbitrary files via a symlink attack on /tmp/magpie_cache.

Patch / fix

  • nagios openstack 3 3.5.1-2.el6ost
  • nagios-common openstack 3 3.5.1-2.el6ost

red hat advisories RHSA-2013:1526

  • nagios openSUSE Tumbleweed 4.4.6-2.5

opensuse advisories openSUSE-SU-2024:11073-1

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

core: html/rss-newsfeed.php insecure temporary file usage

  • Red Hat OpenStack Platform 4 nagios
    affected: no fix available
  • Red Hat Enterprise Linux OpenStack Platform 3.0 nagios 3.5.1-2.el6ost, nagios-common 3.5.1-2.el6ost
    fixed: vendor fix RHSA-2013:1526
  • Red Hat Mobile Application Platform 4 nagios
    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

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

CVSS scores

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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.