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.
CVE-2013-2214 is a security vulnerability that . Impacting 1 product from nagios organizations running these solutions should prioritize assessment and patching.
Documented in 2014, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.
2014-02-10T23:55:04.963
2025-04-11T00:51:21.963
Deferred
CVSSv2: 4.0 (MEDIUM)
AV:N/AC:L/Au:S/C:P/I:N/A:N
8.0
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0 | Yes |
| Application | nagios | nagios | 3.0.1 | Yes |
| Application | nagios | nagios | 3.0.2 | Yes |
| Application | nagios | nagios | 3.0.3 | Yes |
| Application | nagios | nagios | 3.0.4 | Yes |
| Application | nagios | nagios | 3.0.5 | Yes |
| Application | nagios | nagios | 3.0.6 | Yes |
| Application | nagios | nagios | 3.1.0 | Yes |
| Application | nagios | nagios | 3.1.1 | Yes |
| Application | nagios | nagios | 3.1.2 | Yes |
| Application | nagios | nagios | 3.2.0 | Yes |
| Application | nagios | nagios | 3.2.1 | Yes |
| Application | nagios | nagios | 3.2.2 | Yes |
| Application | nagios | nagios | 3.2.3 | Yes |
| Application | nagios | nagios | 3.3.1 | Yes |
| Application | nagios | nagios | 3.4.0 | Yes |
| Application | nagios | nagios | 3.4.1 | Yes |
| Application | nagios | nagios | 3.4.2 | Yes |
| Application | nagios | nagios | 3.4.3 | Yes |
| Application | nagios | nagios | 3.4.4 | Yes |
| Application | nagios | nagios | 3.5.0 | Yes |
| Application | nagios | nagios | 4.0.0 | Yes |
| Application | nagios | nagios | 4.0.0 | Yes |
| Application | nagios | nagios | 4.0.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For nagios's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.