What is CVE-2015-3646?

CVE-2015-3646 is a medium-severity security vulnerability in keystone (pip), affecting versions >= 2014.2, < 2014.2.4. It is fixed in 2014.2.4, 2014.1.5.

Which versions of keystone are affected by CVE-2015-3646?

keystone (pip) versions >= 2014.2, < 2014.2.4 is affected.

Is there a fix for CVE-2015-3646?

Yes. CVE-2015-3646 is fixed in 2014.2.4, 2014.1.5. Upgrade to this version or later.

Is CVE-2015-3646 exploitable, and should I be worried?

Whether CVE-2015-3646 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-2015-3646 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-2015-3646?

Upgrade: keystone to 2014.2.4 or later, keystone to 2014.1.5 or later.

CVE-2015-3646 in keystone | Intelligent Application Security

Q: Which versions of keystone are affected by CVE-2015-3646?

keystone (pip) versions >= 2014.2, < 2014.2.4 is affected.

Q: Is there a fix for CVE-2015-3646?

Yes. CVE-2015-3646 is fixed in 2014.2.4, 2014.1.5. Upgrade to this version or later.

Q: Is CVE-2015-3646 exploitable, and should I be worried?

Whether CVE-2015-3646 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-2015-3646 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-2015-3646?

Upgrade: keystone to 2014.2.4 or later, keystone to 2014.1.5 or later.

Summary

OpenStack Identity (Keystone) before 2014.1.5 and 2014.2.x before 2014.2.4 logs the backend_argument configuration option content, which allows remote authenticated users to obtain passwords and other sensitive backend information by reading the Keystone logs.

Impact

Affected versions

keystone (>= 2014.2, < 2014.2.4) keystone (>= 2011.3, < 2014.1.5)

Security releases

keystone → 2014.2.4 (pip) keystone → 2014.1.5 (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:

keystone to 2014.2.4 or later; keystone to 2014.1.5 or later

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

Frequently Asked Questions

What is CVE-2015-3646? CVE-2015-3646 is a medium-severity security vulnerability in keystone (pip), affecting versions >= 2014.2, < 2014.2.4. It is fixed in 2014.2.4, 2014.1.5.
Which versions of keystone are affected by CVE-2015-3646? keystone (pip) versions >= 2014.2, < 2014.2.4 is affected.
Is there a fix for CVE-2015-3646? Yes. CVE-2015-3646 is fixed in 2014.2.4, 2014.1.5. Upgrade to this version or later.
Is CVE-2015-3646 exploitable, and should I be worried? Whether CVE-2015-3646 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-2015-3646 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-2015-3646?
- Upgrade keystone to 2014.2.4 or later
- Upgrade keystone to 2014.1.5 or later

Other vulnerabilities in keystone

CVE-2026-43000 CVE-2026-44394 CVE-2026-42999 CVE-2026-43001 CVE-2026-40683