# CVE-2016-5801: Auth bypass in OmniMetrix OmniView 1.2

> Weak password requirements in OmniMetrix OmniView allow attackers to gain unauthorized access via brute force attacks.

- **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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w644-rpvw-jrcq

## What is CVE-2016-5801?

CVE-2016-5801 is a high-severity authentication bypass vulnerability in OmniMetrix OmniView 1.2, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in OmniMetrix OmniView, Version 1.2. Insufficient password requirements for the OmniView web application may allow an attacker to gain access by brute forcing account passwords.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Omnimetrix Omniview.

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

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

## Is CVE-2016-5801 being exploited?

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

## Other vulnerabilities in OmniMetrix OmniView 1.2

- [CVE-2016-5786](https://insights.sbomify.com/CVE-2016-5786/): Information disclosure in OmniMetrix OmniView 1.2 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5801 is a high-severity authentication bypass vulnerability in OmniMetrix OmniView 1.2, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5801 in the wild and no public exploit code.

Affected product: OmniMetrix OmniView 1.2. 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-5801/ (Markdown: https://insights.sbomify.com/CVE-2016-5801/index.md)
```

## Sources

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

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