CVE-2020-12692

CVE-2020-12692 is a medium-severity security vulnerability in keystone (pip), affecting versions >= 16.0.0.0rc1, < 16.0.0. It is fixed in 16.0.0, 15.0.1.

Summary

An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.

Impact

CVE-2020-12692 has a CVSS score of 5.4 (Medium). 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 (16.0.0, 15.0.1); upgrading removes the vulnerable code path.

Affected versions

keystone (>= 16.0.0.0rc1, < 16.0.0) keystone (>= 0, < 15.0.1)

Security releases

keystone → 16.0.0 (pip) keystone → 15.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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

keystone to 16.0.0 or later; keystone to 15.0.1 or later

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

Frequently Asked Questions

  1. What is CVE-2020-12692? CVE-2020-12692 is a medium-severity security vulnerability in keystone (pip), affecting versions >= 16.0.0.0rc1, < 16.0.0. It is fixed in 16.0.0, 15.0.1.
  2. How severe is CVE-2020-12692? CVE-2020-12692 has a CVSS score of 5.4 (Medium). 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.
  3. Which versions of keystone are affected by CVE-2020-12692? keystone (pip) versions >= 16.0.0.0rc1, < 16.0.0 is affected.
  4. Is there a fix for CVE-2020-12692? Yes. CVE-2020-12692 is fixed in 16.0.0, 15.0.1. Upgrade to this version or later.
  5. Is CVE-2020-12692 exploitable, and should I be worried? Whether CVE-2020-12692 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
  6. What actually determines whether CVE-2020-12692 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.
  7. How do I fix CVE-2020-12692?
    • Upgrade keystone to 16.0.0 or later
    • Upgrade keystone to 15.0.1 or later

Other vulnerabilities in keystone

Stop the waste.
Protect your environment with Kodem.