Enterprise VirtualizationApplication · Redhat
CVE-2014-8167
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedvdsm and vdsclient does not validate certficate hostname from another vdsm which could facilitate a man-in-the-middle attack
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencevdsm and vdsclient fail to validate that the hostname in SSL/TLS certificates matches the hostname they are connecting to. This allows an attacker with a valid certificate for one domain to intercept traffic destined for another domain, enabling man-in-the-middle attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise VirtualizationApplication
= 3.0
VdsclientApplication
all versions
Virtual Desktop Server ManagerApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if vdsm is installedRun 'rpm -qa | grep -i vdsm' or 'which vdsm' to see if the vdsm package is present on the systemAffected if vdsm package is found installed
-
Check vdsm versionRun 'rpm -q vdsm' or check /usr/share/vdsm for version information. Compare against Red Hat Enterprise Virtualization 3.0Affected if Version is 3.0 or if vdsclient is present at any version
-
Check if vdsclient is installedRun 'rpm -qa | grep -i vdsclient' to see if the vdsclient package is presentAffected if vdsclient package is found at any version
-
Verify SSL/TLS connections are in useCheck vdsm/vdsclient configuration files in /etc/vdsm/ or similar directories for SSL/TLS-enabled connection settings, or inspect network traffic to port 54321 (default vdsm port)Affected if SSL/TLS connections are configured and active with these components
-
Check for hostname validation in SSL handlingReview vdsm source code or logs for certificate hostname validation logic. Look for missing ssl.match_hostname calls or similar validation in the SSL/TLS handshake codeAffected if The code lacks proper CN/SAN hostname validation in SSL/TLS connections
If vdsm version 3.0 or any version of vdsclient is installed and using SSL/TLS connections, the environment is likely affected by missing certificate hostname validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper certificate hostname validation (CN/SAN matching) in all SSL/TLS connections within vdsm and vdsclient, or ensure certificates are properly configured with matching hostnames.
Fix this in Enterprise Virtualization
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-8167 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data