What is CVE-2014-7144?

CVE-2014-7144 is a high-severity security vulnerability in keystonemiddleware (pip), affecting versions < 0.11.0. It is fixed in 0.11.0, 1.2.0.

How severe is CVE-2014-7144?

CVE-2014-7144 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 packages are affected by CVE-2014-7144?

keystonemiddleware (pip) versions = 0, < 0.11.0.

Is there a fix for CVE-2014-7144?

Yes. CVE-2014-7144 is fixed in 0.11.0, 1.2.0. Upgrade to this version or later.

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

Whether CVE-2014-7144 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-7144 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-7144 in keystonemiddleware | Intelligent Application Security

Q: How severe is CVE-2014-7144?

CVE-2014-7144 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 packages are affected by CVE-2014-7144?

keystonemiddleware (pip) versions = 0, < 0.11.0.

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

Yes. CVE-2014-7144 is fixed in 0.11.0, 1.2.0. Upgrade to this version or later.

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

Whether CVE-2014-7144 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-7144 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-7144?

Upgrade: keystonemiddleware to 0.11.0 or later, keystonemiddleware to 1.2.0 or later, python-keystoneclient to 0.11.0 or later, python-keystoneclient to 1.2.0 or later.

Summary

OpenStack keystonemiddleware (formerly python-keystoneclient) 0.x before 0.11.0 and 1.x before 1.2.0 disables certification verification when the "insecure" option is set in a paste configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate.

Impact

CVE-2014-7144 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 (0.11.0, 1.2.0); upgrading removes the vulnerable code path.

Affected versions

keystonemiddleware (< 0.11.0) keystonemiddleware (>= 1.0, < 1.2.0) python-keystoneclient (>= 0, < 0.11.0) python-keystoneclient (>= 1.0, < 1.2.0)

Security releases

keystonemiddleware → 0.11.0 (pip) keystonemiddleware → 1.2.0 (pip) python-keystoneclient → 0.11.0 (pip) python-keystoneclient → 1.2.0 (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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

keystonemiddleware to 0.11.0 or later; keystonemiddleware to 1.2.0 or later; python-keystoneclient to 0.11.0 or later; python-keystoneclient to 1.2.0 or later

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

Frequently Asked Questions

What is CVE-2014-7144? CVE-2014-7144 is a high-severity security vulnerability in keystonemiddleware (pip), affecting versions < 0.11.0. It is fixed in 0.11.0, 1.2.0.
How severe is CVE-2014-7144? CVE-2014-7144 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 packages are affected by CVE-2014-7144?
- keystonemiddleware (pip) (versions < 0.11.0)
- python-keystoneclient (pip) (versions >= 0, < 0.11.0)
Is there a fix for CVE-2014-7144? Yes. CVE-2014-7144 is fixed in 0.11.0, 1.2.0. Upgrade to this version or later.
Is CVE-2014-7144 exploitable, and should I be worried? Whether CVE-2014-7144 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-7144 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-7144?
- Upgrade keystonemiddleware to 0.11.0 or later
- Upgrade keystonemiddleware to 1.2.0 or later
- Upgrade python-keystoneclient to 0.11.0 or later
- Upgrade python-keystoneclient to 1.2.0 or later

Other vulnerabilities in keystonemiddleware

CVE-IDSeverityPackage summary

CVE-2015-1852Highkeystonemiddleware: OpenStack keystonemiddleware and python-keystoneclient vulnerable to man-in-the-middle attacks CVE-2015-7546Highkeystone: OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials