Cloudforms Management EngineApplication · Redhat
CVE-2014-8164
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 · uneditedA insecure configuration for certificate verification (http.verify_mode = OpenSSL::SSL::VERIFY_NONE) may lead to verification bypass in Red Hat CloudForms 5.x.
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 confidenceRed Hat CloudForms 5.x has an insecure SSL/TLS configuration where the HTTP client is set to OpenSSL::SSL::VERIFY_NONE, disabling certificate verification. This allows man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates.
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
Cloudforms Management EngineApplication
= 5.0CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify CloudForms installation and versionCheck the installed version of Red Hat CloudForms Management Engine using rpm, yum, or the web UI (typically under About or Settings).Affected if The installed version is 5.0 (specifically 5.0.x series).
-
Locate SSL/TLS client configurationSearch for Ruby configuration files or scripts that initialize OpenSSL::SSL::VERIFY_NONE in the CloudForms installation directory, typically under /var/www/miq/ or /opt/rh/cfme/.Affected if Code is found that sets SSL verification mode to VERIFY_NONE.
-
Inspect HTTP client verify_mode settingExamine the HTTP client configuration files or code that uses OpenSSL for SSL connections. Look for the verify_mode parameter set to OpenSSL::SSL::VERIFY_NONE.Affected if The verify_mode is explicitly set to OpenSSL::SSL::VERIFY_NONE, disabling certificate validation.
-
Check for certificate validation in SSL connectionsReview any custom scripts or configurations that create HTTPS connections using Ruby's Net::HTTP or similar libraries with verify_mode disabled.Affected if HTTPS connections are made without proper certificate chain validation.
A user is affected if they run Red Hat CloudForms Management Engine version 5.0 and the SSL verify_mode is set to OpenSSL::SSL::VERIFY_NONE in any HTTP client configuration.
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 dataChange the http.verify_mode setting from OpenSSL::SSL::VERIFY_NONE to OpenSSL::SSL::VERIFY_PEER (or VERIFY_PEER | VERIFY_CLIENT_ONCE) to enable proper SSL certificate validation.
Fix this in Cloudforms Management Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8164 — 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-8164 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