First published: Fri Aug 24 2012(Updated: )
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] <a href="http://wiki.ovirt.org/wiki/Release_Notes#Interfaces">http://wiki.ovirt.org/wiki/Release_Notes#Interfaces</a> [2] <a href="http://gerrit.ovirt.org/#/c/7209/">http://gerrit.ovirt.org/#/c/7209/</a> [3] <a href="http://gerrit.ovirt.org/#/c/7249/">http://gerrit.ovirt.org/#/c/7249/</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/ovirt-engine-sdk-python-3.4.0.7 | <1 | 1 |
Ovirt | =3.1 | |
Ovirt Ovirt-engine-cli | <=3.1.0.5 | |
Ovirt-engine-sdk 3.1.0.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-3533 is classified as a moderate severity vulnerability due to the potential for man-in-the-middle attacks.
To mitigate CVE-2012-3533, upgrade to a version of oVirt that properly validates SSL certificates.
CVE-2012-3533 affects oVirt version 3.1, as well as the related oVirt engine SDK versions up to 3.4.0.7.
The primary impact of CVE-2012-3533 is the risk of unauthorized data interception and manipulation during client-server communications.
Yes, later versions of oVirt have implemented proper SSL certificate validation to address the issues outlined in CVE-2012-3533.