# CVE-2013-2214: Information disclosure in n/a

> Authenticated users can view sensitive hostname information for services they are not authorized to access via the status interface.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x8j3-jcqf-xvvp

## What is CVE-2013-2214?

CVE-2013-2214 is a medium-severity vulnerability in n/a, published on 10 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2214?

It affects 1 product.


Products: Nagios Nagios.

## How do I fix CVE-2013-2214?

Upgrade to a fixed version.

## Is CVE-2013-2214 being exploited?

There is no known exploitation of CVE-2013-2214 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2002-1959](https://insights.sbomify.com/CVE-2002-1959/): Command injection in n/a (critical 10.0)
- [CVE-2016-0726](https://insights.sbomify.com/CVE-2016-0726/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2008-7313](https://insights.sbomify.com/CVE-2008-7313/): Command injection in n/a (critical 9.8)
- [CVE-2014-5009](https://insights.sbomify.com/CVE-2014-5009/): Command injection in n/a (critical 9.8)
- [CVE-2016-9565](https://insights.sbomify.com/CVE-2016-9565/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2214 and fix it if it is affected.

What it is: CVE-2013-2214 is a medium-severity vulnerability in n/a, published on 10 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2214 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2214/ (Markdown: https://insights.sbomify.com/CVE-2013-2214/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2214
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2214
- OSV: https://osv.dev/vulnerability/CVE-2013-2214

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2214/
Summaries are generated and may contain mistakes; the official description above is the record.