# CVE-2016-10367: Path traversal in n/a

> Unauthenticated attackers can read arbitrary files via directory traversal using URL encoding bypass in Opsview Monitor Pro.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mx48-vw4g-gmrc

## What is CVE-2016-10367?

CVE-2016-10367 is a high-severity path traversal vulnerability in n/a, published on 3 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Opsview Monitor Pro (Prior to 5.1.0.162300841, prior to 5.0.2.27475, prior to 4.6.4.162391051, and 4.5.x without a certain 2016 security patch), an unauthenticated Directory Traversal vulnerability can be exploited by issuing a specially crafted HTTP GET request utilizing a simple URL encoding bypass, %252f instead of /.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2016-10367?

It affects 1 product.


Products: Opsview Opsview.

## How do I fix CVE-2016-10367?

No fix has been published for CVE-2016-10367 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-10367 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10367 exists.

Public exploit code:

- Opsview Monitor Pro - Local File Inclusion (nuclei): http/cves/2016/CVE-2016-10367.yaml

## Other vulnerabilities in n/a

- [CVE-2018-16144](https://insights.sbomify.com/CVE-2018-16144/): Command injection in n/a (critical 9.8)
- [CVE-2013-3935](https://insights.sbomify.com/CVE-2013-3935/): Cross-site request forgery in Opsview (high 8.8)
- [CVE-2018-16145](https://insights.sbomify.com/CVE-2018-16145/): Privilege escalation in n/a (high 8.1)
- [CVE-2013-5694](https://insights.sbomify.com/CVE-2013-5694/): SQL injection in n/a (high 7.5)
- [CVE-2018-16146](https://insights.sbomify.com/CVE-2018-16146/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10367 and fix it if it is affected.

What it is: CVE-2016-10367 is a high-severity path traversal vulnerability in n/a, published on 3 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10367 exists.

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-2016-10367/ (Markdown: https://insights.sbomify.com/CVE-2016-10367/index.md)
```

## Sources

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

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