Skip to content
Fencer Intel
medium 4.0

CVE-2013-2214 json

status.cgi in Nagios 4.0 before 4.0 beta4 and 3.x before 3.5.1 does not properly restrict access to certain users that are a contact for a…

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

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

Summary

status.cgi in Nagios 4.0 before 4.0 beta4 and 3.x before 3.5.1 does not properly restrict access to certain users that are a contact for a service, which allows remote authenticated users to obtain sensitive information about hostnames via the servicegroup (1) overview, (2) summary, or (3) grid style in status.cgi. NOTE: this behavior is by design in most 3.x versions, but the upstream vendor "decided to change it for Nagios 4" and 3.5.1.

Patch / fix

  • nagios openSUSE Tumbleweed 4.4.6-2.5

opensuse advisories openSUSE-SU-2024:11073-1

Is CVE-2013-2214 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-2214 updated cvss 4.0

nagios: unauthorized hosts and services displayed in servicegroup view

  • Red Hat OpenStack Platform 3 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

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

CVSS scores

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

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.