Skip to content
Fencer Intel
medium 4.0

CVE-2014-3485 json

The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to r…

published 2014-07-11 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-3492

cvss
4.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

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.

Patch / fix

  • rhevm rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-lib rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-setup rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-tools rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-backend rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-restapi rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-dbscripts rhev manager 3 3.4.0-0.22.el6ev
  • rhevm-setup-base rhev manager 3 3.4.0-0.22.el6ev

red hat advisories RHSA-2014:0814

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-3485 updated cvss 4.0

ovirt-engine-api: XML eXternal Entity (XXE) flaw

  • Red Hat RHEV-M 3.4 rhevm 3.4.0-0.22.el6ev, rhevm-lib 3.4.0-0.22.el6ev, rhevm-setup 3.4.0-0.22.el6ev, rhevm-tools 3.4.0-0.22.el6ev, rhevm-backend 3.4.0-0.22.el6ev, rhevm-restapi 3.4.0-0.22.el6ev, +9 more
    fixed: vendor fix RHSA-2014:0814

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.