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

> Remote attackers can read arbitrary files via crafted XML documents due to insecure DocumentBuilderFactory configuration in oVirt Engine.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6whg-r3w4-fhjh, RHSA-2014:1161

## What is CVE-2014-3573?

CVE-2014-3573 is a medium-severity vulnerability in n/a, published on 18 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The oVirt Engine backend module, as used in Red Hat Enterprise Virtualization Manager before 3.4.2, uses an "insecure DocumentBuilderFactory," which allows remote attackers to read arbitrary files or possibly have other unspecified impact via a crafted XML/RSDL document, related to an XML External Entity (XXE) issue.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


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

Products: Redhat Enterprise Virtualization Manager.

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

Upgrade to a fixed version.

## Is CVE-2014-3573 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7544](https://insights.sbomify.com/CVE-2015-7544/): Command injection in n/a (critical 9.1)
- [CVE-2015-0237](https://insights.sbomify.com/CVE-2015-0237/): Missing authorization in n/a (medium 6.8)
- [CVE-2012-0861](https://insights.sbomify.com/CVE-2012-0861/): Security feature bypass in n/a (medium 6.8)
- [CVE-2010-2793](https://insights.sbomify.com/CVE-2010-2793/): Race condition in n/a (medium 6.8)
- [CVE-2012-0860](https://insights.sbomify.com/CVE-2012-0860/): Path traversal in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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