# CVE-2014-7851: Auth bypass in n/a

> Authenticated attackers can hijack sessions by reusing tokens after logout, gaining other users' privileges in oVirt.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-353g-73mj-6wf9, RHBA-2015:0230

## What is CVE-2014-7851?

CVE-2014-7851 is a high-severity authentication bypass vulnerability in n/a, published on 16 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

oVirt 3.2.2 through 3.5.0 does not invalidate the restapi session after logout from the webadmin, which allows remote authenticated users with knowledge of another user's session data to gain that user's privileges by replacing their session token with that of another user.

Weakness: CWE-264

## Which versions are affected by CVE-2014-7851?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rhevm` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-backend` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-dbscripts` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-extensions-api-impl` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-extensions-api-impl-javadoc` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-lib` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-restapi` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup-base` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup-plugin-allinone` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup-plugin-ovirt-engine` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup-plugin-ovirt-engine-common` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-setup-plugin-websocket-proxy` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-tools` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-userportal` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-webadmin-portal` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |
| `rhevm-websocket-proxy` | Red Hat:rhev_manager:3 | All versions | 0:3.5.0-0.32.el6ev |

Products: Ovirt Ovirt, Redhat Ovirt-Engine.

## How do I fix CVE-2014-7851?

Apply the vendor's patch.

## Is CVE-2014-7851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1074](https://insights.sbomify.com/CVE-2018-1074/): Information disclosure in ovirt-engine (high 7.7)
- [CVE-2017-15113](https://insights.sbomify.com/CVE-2017-15113/): Information disclosure in ovirt-engine (high 7.2)
- [CVE-2014-0152](https://insights.sbomify.com/CVE-2014-0152/): Auth bypass in n/a (medium 6.8)
- [CVE-2019-3879](https://insights.sbomify.com/CVE-2019-3879/): Missing authorization in ovirt-engine (medium 6.5)
- [CVE-2019-10194](https://insights.sbomify.com/CVE-2019-10194/): Information disclosure in ovirt-engine-metrics (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7851 and fix it if it is affected.

What it is: CVE-2014-7851 is a high-severity authentication bypass vulnerability in n/a, published on 16 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-7851 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-2014-7851/ (Markdown: https://insights.sbomify.com/CVE-2014-7851/index.md)
```

## Sources

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

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