Red Hat Enterprise Virtualization Manager (aka RHEV-M) 2.2

CPE Details

Red Hat Enterprise Virtualization Manager (aka RHEV-M) 2.2
redhat
enterprise_virtualization_manager
2.2
2013-01-11
17h05 +00:00
2013-01-15
17h19 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:o:redhat:enterprise_virtualization_manager:2.2:*:*:*:*:*:*:*

Informations

Vendor

redhat

Product

enterprise_virtualization_manager

Version

2.2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2009-3552 2019-11-09 01h32 +00:00 In RHEV-M VDC 2.2.0, it was found that the SSL certificate was not verified when using the client-side Red Hat Enterprise Virtualization Manager interface (a Windows Presentation Foundation (WPF) XAML browser application) to connect to the Red Hat Enterprise Virtualization Manager. An attacker on the local network could use this flaw to conduct a man-in-the-middle attack, tricking the user into thinking they are viewing the Red Hat Enterprise Virtualization Manager when the content is actually attacker-controlled, or modifying actions a user requested Red Hat Enterprise Virtualization Manager to perform.
3.1
Low
CVE-2012-0860 2013-01-04 21h00 +00:00 Multiple untrusted search path vulnerabilities in Red Hat Enterprise Virtualization Manager (RHEV-M) before 3.1, when adding a host, allow local users to gain privileges via a Trojan horse (1) deployUtil.py or (2) vds_bootstrap.py Python module in /tmp/.
6.2
CVE-2012-5516 2013-01-04 21h00 +00:00 Red Hat Enterprise Virtualization Manager (RHEV-M) before 3.1, when moving disks between storage domains, does not properly wipe-after-delete, which prevents disks from being securely deleted and might allow local users to obtain sensitive information via unspecified vectors.
2.1
CVE-2010-2793 2010-12-08 17h00 +00:00 Race condition in the SPICE (aka spice-activex) plug-in for Internet Explorer in Red Hat Enterprise Virtualization (RHEV) Manager before 2.2.4 allows local users to create a certain named pipe, and consequently gain privileges, via vectors involving knowledge of the name of this named pipe, in conjunction with use of the ImpersonateNamedPipeClient function.
6.8