Enterprise MrgApplication · Redhat
CVE-2014-3706
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 · uneditedovirt-engine, as used in Red Hat MRG 3, allows man-in-the-middle attackers to spoof servers by leveraging failure to verify key attributes in vdsm X.509 certificates.
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 ovirt-engine fails to verify critical attributes in vdsm X.509 certificates, allowing man-in-the-middle attackers to impersonate servers by presenting fraudulent certificates that bypass proper validation checks.
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 MrgApplication
= 3.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/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.
-
Confirm ovirt-engine installationCheck if ovirt-engine is installed by querying the package manager (rpm -qa | grep ovirt-engine) or checking for /usr/share/ovirt-engine directoryAffected if ovirt-engine package version 3.0.x from Red Hat Enterprise MRG is found on the system
-
Verify vdsm integration is activeCheck if vdsm (Virtual Desktop Server Manager) service is running and configured with ovirt-engine by reviewing /etc/vdsm/vdsm.conf and running systemctl status vdsmdAffected if vdsm service is running and configured to communicate with ovirt-engine
-
Inspect SSL/TLS certificate configurationExamine the SSL certificate configuration files in /etc/pki/ovirt-engine/ and /etc/vdsm/ssl.conf for the vdsm certificate settingsAffected if vdsm certificates are present but no explicit attribute validation (key usage, subject, issuer) is configured in the ovirt-engine trust settings
-
Check certificate validation logic in ovirt-engineReview the ovirt-engine web app configuration and Java keystore settings for SSL certificate validation: ls -la /etc/ovirt-engine/ and look for truststore configurationsAffected if The ovirt-engine truststore exists but the validation code does not verify certificate critical extensions such as keyUsage or extendedKeyUsage
-
Test for missing certificate attribute verificationExamine the SSLValidator or similar validation classes in ovirt-engine if accessible: grep -r 'validate.*cert' /usr/share/ovirt-engine/ or check audit logs for certificate acceptance without full validationAffected if Certificate validation accepts certificates without checking subject/issuer fields or trust chain integrity
A system is affected if it runs Red Hat Enterprise MRG 3.0 with ovirt-engine and vdsm integration, where SSL certificate validation does not verify critical X.509 certificate attributes and trust chain.
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 X.509 certificate validation in ovirt-engine, including verification of certificate key attributes, subject/issuer validation, and proper trust chain verification.
Fix this in Enterprise Mrg
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3706 — 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-3706 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