CloudformsApplication · Redhat
CVE-2017-2639
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 · uneditedIt was found that CloudForms does not verify that the server hostname matches the domain name in the certificate when using a custom CA and communicating with Red Hat Virtualization (RHEV) and OpenShift. This would allow an attacker to spoof RHEV or OpenShift systems and potentially harvest sensitive information from CloudForms.
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 confidenceCloudForms fails to perform TLS hostname verification when using a custom Certificate Authority to communicate with Red Hat Virtualization (RHEV) and OpenShift. The application validates the certificate chain but does not verify that the server's hostname matches the domain name in the certificate, allowing an attacker to spoof the RHEV or OpenShift endpoints and intercept sensitive communications.
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
CloudformsApplication
= 4.5
Cloudforms Management EngineApplication
= 5.8CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Determine the installed CloudForms versionUse the CloudForms management interface or check the product version via the about page in the web UI, or run 'grep version' on the applianceAffected if The installed version is 4.5 for Red Hat CloudForms or 5.8 for CloudForms Management Engine
-
Check if a RHEV provider is configuredNavigate to Compute > Infrastructure > Red Hat Virtualization in the CloudForms web UI, or query the database for providers of type 'RHEV'Affected if A RHEV provider is added and configured in CloudForms
-
Check if an OpenShift provider is configuredNavigate to Containers > Providers in the CloudForms web UI, or query the database for providers of type 'OpenShift'Affected if An OpenShift container provider is added and configured in CloudForms
-
Determine if a custom Certificate Authority is in useInspect the SSL/TLS settings for the RHEV or OpenShift provider in CloudForms, or check the CA bundle configuration file used for provider communicationsAffected if A custom CA certificate is configured for communicating with RHEV or OpenShift (instead of using the system default CA bundle)
If you are running CloudForms 4.5 or CloudForms Management Engine 5.8 with a RHEV or OpenShift provider configured that uses a custom CA certificate, then your environment is affected by this vulnerability because hostname verification is not performed.
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 TLS hostname verification in CloudForms when establishing connections to RHEV and OpenShift, ensuring the server's hostname matches the CN/SAN in the certificate.
Fix this in Cloudforms
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2639 — 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-2017-2639 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