RbovirtApplication · Amos Benari
CVE-2014-0036
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 · uneditedThe rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.
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 confidenceThe rbovirt gem before version 0.0.24 uses the rest-client HTTP library with SSL certificate verification disabled. This allows remote attackers to intercept communications between the gem and the oVirt API server via man-in-the-middle attacks, as the client does not verify the server's SSL certificate.
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
RbovirtApplication
<= 0.0.23= 0.0.1= 0.0.2= 0.0.3= 0.0.4= 0.0.5= 0.0.6= 0.0.7= 0.0.8= 0.0.9= 0.0.10= 0.0.11CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 if rbovirt gem is in useSearch your codebase for references to 'rbovirt' in Gemfile, gemspec files, or Ruby source files that require the gem. Check output of 'gem list rbovirt' if you have CLI access.Affected if The rbovirt gem is present in your environment
-
Determine installed rbovirt versionRun 'gem list rbovirt' or check your Gemfile.lock for the rbovirt version entry. Compare the version number against the affected range (0.0.1 through 0.0.11, or any version <= 0.0.23).Affected if The installed version is 0.0.23 or earlier, or matches any of 0.0.1 through 0.0.11
-
Locate rest-client usage in rbovirt codeExamine the rbovirt gem source code or your bundled gem files. Look for the rest-client initialization code where HTTP requests to the oVirt API are made.Affected if rest-client is used without explicit SSL verification configuration
-
Check for disabled SSL verificationInspect the rest-client configuration calls within the rbovirt gem code. Look for patterns such as 'verify_ssl: false', 'ssl_verify: false', or RestClient::Request.new with verification disabled. Also check for any RestClient.disable_ssl_cert_validation calls.Affected if SSL certificate verification is explicitly disabled or not enabled in the rest-client configuration used for oVirt API connections
Your environment is affected if the rbovirt gem version is 0.0.23 or earlier (including 0.0.1 through 0.0.11) AND the gem is used to connect to an oVirt API server without SSL verification being explicitly enabled.
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 dataUpgrade the rbovirt gem to version 0.0.24 or later which enables SSL verification in the rest-client configuration. If upgrading is not immediately possible, explicitly enable SSL verification in rest-client or use a custom CA bundle.
Fix this in Rbovirt
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0036 — 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-0036 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