Bug 1165015 (CVE-2014-8167) - CVE-2014-8167 vdsm and vdsclient: does not validate certficate hostname from another vdsm
Summary: CVE-2014-8167 vdsm and vdsclient: does not validate certficate hostname from ...
Alias: CVE-2014-8167
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
: 1165022 (view as bug list)
Depends On: 1060717 1164978 1165464 1165476
Blocks: 1164675
TreeView+ depends on / blocked
Reported: 2014-11-18 06:39 UTC by Wade Mealing
Modified: 2019-09-29 13:23 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that the VDSM SSL certificate validation implementation did not check whether the server host name matched the domain name in a subject's Common Name (CN) field in a X.509 certificate. A man-in-the-middle attacker could use this flaw to spoof a VDSM server using a specially crafted X.509 certificate.
Clone Of:
Last Closed: 2015-07-14 17:51:00 UTC

Attachments (Terms of Use)

Description Wade Mealing 2014-11-18 06:39:32 UTC
Multiple security flaws were found in the vdsm SSL certificate validation code. Details:

VDSM can connect to other VDSM services for remote management of virtual hosts stored on a remote node. During the connection the remote node presents a certificate.  The hostname of the remote host is presented in the certificate but not validated by the client connection to ensure that the host matches the correct name.  The SSL client should compare the hostname presented in the certificate to the host name returned in the server certificates "Common Name" field of the "subjectDN" entry. If this is not the case the connection should fail

Comment 3 Kurt Seifried 2015-02-12 05:35:44 UTC
*** Bug 1165022 has been marked as a duplicate of this bug. ***

Comment 4 Kurt Seifried 2015-07-14 17:46:29 UTC
As per discussion with Alon Bar-Lev this may be addressed in RHEV 4.

Comment 5 Kurt Seifried 2015-07-14 17:51:00 UTC

This issue affects the versions of vdsm as shipped with Red Hat Enterprise Vitalization 3.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.