What is CVE-2017-12440?

CVE-2017-12440 is a high-severity missing authentication for critical function vulnerability in aodh (pip), affecting versions < 6.0.1. It is fixed in 6.0.1. A critical operation is accessible without requiring any authentication.

How severe is CVE-2017-12440?

CVE-2017-12440 has a CVSS score of 7.5 (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 aodh are affected by CVE-2017-12440?

aodh (pip) versions < 6.0.1 is affected.

Is there a fix for CVE-2017-12440?

Yes. CVE-2017-12440 is fixed in 6.0.1. Upgrade to this version or later.

Is CVE-2017-12440 exploitable, and should I be worried?

Whether CVE-2017-12440 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-2017-12440 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-2017-12440 in aodh

Q: How severe is CVE-2017-12440?

CVE-2017-12440 has a CVSS score of 7.5 (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 aodh are affected by CVE-2017-12440?

aodh (pip) versions < 6.0.1 is affected.

Q: Is there a fix for CVE-2017-12440?

Yes. CVE-2017-12440 is fixed in 6.0.1. Upgrade to this version or later.

Q: Is CVE-2017-12440 exploitable, and should I be worried?

Whether CVE-2017-12440 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-2017-12440 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-2017-12440?

Upgrade aodh to 6.0.1 or later.

Summary

Openstack Aodh can be used to launder Keystone trusts

Aodh as packaged in Openstack Ocata and Newton before change-ID I8fd11a7f9fe3c0ea5f9843a89686ac06713b7851 and before Pike-rc1 does not verify that trust IDs belong to the user when creating alarm action with the scheme trust+http, which allows remote authenticated users with knowledge of trust IDs where Aodh is the trustee to obtain a Keystone token and perform unspecified authenticated actions by adding an alarm action with the scheme trust+http, and providing a trust id where Aodh is the trustee.

Impact

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2017-12440 has a CVSS score of 7.5 (High). The vector is network-reachable, low 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 (6.0.1); upgrading removes the vulnerable code path.

Affected versions

aodh (< 6.0.1)

Security releases

aodh → 6.0.1 (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 aodh to 6.0.1 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2017-12440? CVE-2017-12440 is a high-severity missing authentication for critical function vulnerability in aodh (pip), affecting versions < 6.0.1. It is fixed in 6.0.1. A critical operation is accessible without requiring any authentication.
How severe is CVE-2017-12440? CVE-2017-12440 has a CVSS score of 7.5 (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 aodh are affected by CVE-2017-12440? aodh (pip) versions < 6.0.1 is affected.
Is there a fix for CVE-2017-12440? Yes. CVE-2017-12440 is fixed in 6.0.1. Upgrade to this version or later.
Is CVE-2017-12440 exploitable, and should I be worried? Whether CVE-2017-12440 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-2017-12440 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-2017-12440? Upgrade aodh to 6.0.1 or later.