CVE-2014-0161
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-sdk-python before 3.4.0.7 and 3.5.0.4 does not verify that the hostname of the remote endpoint matches the Common Name (CN) or subjectAltName as specified by its x.509 certificate in a TLS/SSL session. This could allow man-in-the-middle attackers to spoof remote endpoints via an arbitrary valid certificate.
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-sdk-python fails to validate that the hostname in a TLS/SSL connection matches the certificate's Common Name (CN) or subjectAltName field. This allows attackers to intercept encrypted connections by presenting any valid certificate, 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< 3.4.0.7>= 3.5.0.0, < 3.5.0.4CVSS 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.
-
Find installed ovirt-engine-sdk-python versionRun 'pip show ovirt-engine-sdk-python' or 'pip list | grep -i ovirt' to see the installed versionAffected if The version shown is less than 3.4.0.7, or is 3.5.0.0 through 3.5.0.3
-
Check Python site-packages for vulnerable versionLocate the package directory (typically site-packages/ovirt-engine-sdk-python) and check the version file or run 'python -c "import ovirtsdk; print(ovirtsdk.__version__)"'Affected if The printed version matches the affected ranges above
-
Identify code using SSL/TLS connectionsSearch project code for 'ovirtsdk' imports that create connections to Ovirt servers, especially uses of 'API' class or 'connect()' method with HTTPS URLsAffected if The code establishes HTTPS connections to Ovirt hosts and the SDK version is vulnerable
-
Verify if hostname verification is missingInspect SDK source code in the connection module for 'check_hostname' or 'verify' SSL context settings; if absent or set to False, the vulnerability appliesAffected if SSL context is configured without hostname verification and SDK version is in affected range
You are affected if the installed ovirt-engine-sdk-python version is below 3.4.0.7 or between 3.5.0.0 and 3.5.0.3 inclusive, and your code uses it to make HTTPS connections to Ovirt servers.
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 data3.4.0.73.5.0.4
Update ovirt-engine-sdk-python to version 3.4.0.7 or later for the 3.4.x branch, or 3.5.0.4 or later for the 3.5.x branch, which implement proper hostname verification.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0161 — 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-0161 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