What is CVE-2014-0161?

CVE-2014-0161 is a high-severity security vulnerability in ovirt-engine-sdk-python (pip), affecting versions < 3.4.0.7. It is fixed in 3.4.0.7, 3.5.0.4.

How severe is CVE-2014-0161?

CVE-2014-0161 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ovirt-engine-sdk-python are affected by CVE-2014-0161?

ovirt-engine-sdk-python (pip) versions < 3.4.0.7 is affected.

Is there a fix for CVE-2014-0161?

Yes. CVE-2014-0161 is fixed in 3.4.0.7, 3.5.0.4. Upgrade to this version or later.

Is CVE-2014-0161 exploitable, and should I be worried?

Whether CVE-2014-0161 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-0161 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2014-0161 in ovirt-engine-sdk-python

Q: How severe is CVE-2014-0161?

CVE-2014-0161 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ovirt-engine-sdk-python are affected by CVE-2014-0161?

ovirt-engine-sdk-python (pip) versions < 3.4.0.7 is affected.

Q: Is there a fix for CVE-2014-0161?

Yes. CVE-2014-0161 is fixed in 3.4.0.7, 3.5.0.4. Upgrade to this version or later.

Q: Is CVE-2014-0161 exploitable, and should I be worried?

Whether CVE-2014-0161 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-0161 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-0161?

Upgrade: ovirt-engine-sdk-python to 3.4.0.7 or later, ovirt-engine-sdk-python to 3.5.0.4 or later.

Summary

ovirt-engine-sdk-python improper validation of hostname in x.509 certificate

ovirt-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.

Impact

CVE-2014-0161 has a CVSS score of 5.9 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.4.0.7, 3.5.0.4); upgrading removes the vulnerable code path.

Affected versions

ovirt-engine-sdk-python (< 3.4.0.7) ovirt-engine-sdk-python (>= 3.5.0.0, < 3.5.0.4)

Security releases

ovirt-engine-sdk-python → 3.4.0.7 (pip) ovirt-engine-sdk-python → 3.5.0.4 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

ovirt-engine-sdk-python to 3.4.0.7 or later; ovirt-engine-sdk-python to 3.5.0.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2014-0161? CVE-2014-0161 is a high-severity security vulnerability in ovirt-engine-sdk-python (pip), affecting versions < 3.4.0.7. It is fixed in 3.4.0.7, 3.5.0.4.
How severe is CVE-2014-0161? CVE-2014-0161 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ovirt-engine-sdk-python are affected by CVE-2014-0161? ovirt-engine-sdk-python (pip) versions < 3.4.0.7 is affected.
Is there a fix for CVE-2014-0161? Yes. CVE-2014-0161 is fixed in 3.4.0.7, 3.5.0.4. Upgrade to this version or later.
Is CVE-2014-0161 exploitable, and should I be worried? Whether CVE-2014-0161 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-0161 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-0161?
- Upgrade ovirt-engine-sdk-python to 3.4.0.7 or later
- Upgrade ovirt-engine-sdk-python to 3.5.0.4 or later