# CVE-2014-3485: XML external entity in n/a

> Authenticated attackers can exploit an XML External Entity vulnerability in the oVirt REST API to read arbitrary files on the server.

- **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:** 11 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6g69-jrpm-4wp2, RHSA-2014:0814

## What is CVE-2014-3485?

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

### Official description

The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


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

Products: Redhat Enterprise Virtualization.

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

Apply the vendor's patch.

## Is CVE-2014-3485 being exploited?

There is no known exploitation of CVE-2014-3485 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-2014-3485 and fix it if it is affected.

What it is: CVE-2014-3485 is a medium-severity vulnerability in n/a, published on 11 Jul 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-2014-3485 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-3485/ (Markdown: https://insights.sbomify.com/CVE-2014-3485/index.md)
```

## Sources

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

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