# CVE-2015-1841: Security feature bypass in n/a

> Local users can bypass the Web Admin interface timeout by selecting a VM, potentially maintaining unauthorized access.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hf5q-rvmp-xhfh

## What is CVE-2015-1841?

CVE-2015-1841 is a low-severity vulnerability in n/a, published on 8 Sep 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Web Admin interface in Red Hat Enterprise Virtualization Manager (RHEV-M) allows local users to bypass the timeout function by selecting a VM in the VM grid view.

Weakness: CWE-17

## Which versions are affected by CVE-2015-1841?

It affects 1 product.


Products: Redhat Enterprise Virtualization.

## How do I fix CVE-2015-1841?

Apply the vendor's patch.

## Is CVE-2015-1841 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5201](https://insights.sbomify.com/CVE-2015-5201/): Auth bypass in Enterprise Virtualization Hypervisor (aka RHEV-H) (high 7.5)
- [CVE-2013-2151](https://insights.sbomify.com/CVE-2013-2151/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2152](https://insights.sbomify.com/CVE-2013-2152/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2176](https://insights.sbomify.com/CVE-2013-2176/): Privilege escalation in n/a (high 7.2)
- [CVE-2017-2614](https://insights.sbomify.com/CVE-2017-2614/): Auth bypass in ovirt-engine-extension-aaa-jdbc (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1841 and fix it if it is affected.

What it is: CVE-2015-1841 is a low-severity vulnerability in n/a, published on 8 Sep 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-1841 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-2015-1841/ (Markdown: https://insights.sbomify.com/CVE-2015-1841/index.md)
```

## Sources

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

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