CVE-2013-2214
Last modified
CVE-2013-2214 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 4.34% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Nagios | Nagios | 3.0 | — |
| Nagios | Nagios | 3.0.1 | — |
| Nagios | Nagios | 3.0.2 | — |
| Nagios | Nagios | 3.0.3 | — |
| Nagios | Nagios | 3.0.4 | — |
| Nagios | Nagios | 3.0.5 | — |
| Nagios | Nagios | 3.0.6 | — |
| Nagios | Nagios | 3.1.0 | — |
| Nagios | Nagios | 3.1.1 | — |
| Nagios | Nagios | 3.1.2 | — |
| Nagios | Nagios | 3.2.0 | — |
| Nagios | Nagios | 3.2.1 | — |
| Nagios | Nagios | 3.2.2 | — |
| Nagios | Nagios | 3.2.3 | — |
| Nagios | Nagios | 3.3.1 | — |
| Nagios | Nagios | 3.4.0 | — |
| Nagios | Nagios | 3.4.1 | — |
| Nagios | Nagios | 3.4.2 | — |
| Nagios | Nagios | 3.4.3 | — |
| Nagios | Nagios | 3.4.4 | — |
| Nagios | Nagios | 3.5.0 | — |
| Nagios | Nagios | 4.0.0 | Beta1 |
References
- http://tracker.nagios.org/view.php?id=456Vendor Advisory
- http://tracker.nagios.org/view.php?id=456Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-2214?
How severe is CVE-2013-2214?
How do I fix CVE-2013-2214?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-2208tpp 1.3.1 allows remote attackers to execute arbitrary comma…
- CVE-2013-2209Cross-site scripting (XSS) vulnerability in the auto-complet…
- CVE-2013-2210Heap-based buffer overflow in the XML Signature Reference fu…
- CVE-2013-2211The libxenlight (libxl) toolstack library in Xen 4.0.x, 4.1.…
- CVE-2013-2212The vmx_set_uc_mode function in Xen 3.3 through 4.3, when di…
- CVE-2013-2213The KRandom::random function in KDE Paste Applet after 4.10.…5.5
- CVE-2013-2215Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2013-2216Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2013-2217cache.py in Suds 0.4, when tempdir is set to None, allows lo…
- CVE-2013-2218Double free vulnerability in the virConnectListAllInterfaces…
- CVE-2013-2219The Red Hat Directory Server before 8.2.11-13 and 389 Direct…
- CVE-2013-2220Buffer overflow in the radius_get_vendor_attr function in th…
Are you affected by CVE-2013-2214?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST