CVE-2012-3533: Medium severity ovirt vulnerability
It was reported that oVirt 3.1 did not properly validate SSL certificates of the server when the client would connect. This could permit man-in-the-middle attacks.
In oVirt sdk, the python httplib.HTTPSConnection function is used to let the programmer specify the client's pair of certificates, but does not force the underlying SSL library to check the server certificate against the client keys.
Because of this, the oVirt CLI tool does not check certificates upon connection.
The new python SDK (ovirt-engine-sdk) and new python CLI (ovirt-engine-cli) were introduced in oVirt 3.1 [1] ; earlier versions are not affected by this flaw.
This has been corrected in upstream git for the sdk [2] and the cli [3].
[1] http://wiki.ovirt.org/wiki/ReleaseNotes#Interfaces [2] http://gerrit.ovirt.org/#/c/7209/ [3] http://gerrit.ovirt.org/#/c/7249/
Other sources
The python SDK before 3.1.0.6 and CLI before 3.1.0.8 for oVirt 3.1 does not check the server SSL certificate against the client keys, which allows remote attackers to spoof a server via a man-in-the-middle (MITM) attack.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-3533?
CVE-2012-3533 is classified as a moderate severity vulnerability due to the potential for man-in-the-middle attacks.
How do I fix CVE-2012-3533?
To mitigate CVE-2012-3533, upgrade to a version of oVirt that properly validates SSL certificates.
What versions of oVirt are affected by CVE-2012-3533?
CVE-2012-3533 affects oVirt version 3.1, as well as the related oVirt engine SDK versions up to 3.4.0.7.
What are the potential impacts of CVE-2012-3533?
The primary impact of CVE-2012-3533 is the risk of unauthorized data interception and manipulation during client-server communications.
Is CVE-2012-3533 fixed in later versions of oVirt?
Yes, later versions of oVirt have implemented proper SSL certificate validation to address the issues outlined in CVE-2012-3533.