# CVE-2020-12692: OpenStack Keystone does not check signature TTL of the EC2 credential auth method

Source: https://junglewise.ai/threats/cve-2020-12692-openstack-keystone-does-not-check-signature-ttl-of-the-ec2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-05-07  
License: CC BY 4.0 with a link back

CVE-2020-12692 · Severity: low · CVSS 3.1 · Published 2020-05-07

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.

Technologies: [keystone (PyPI)](https://junglewise.ai/threats/technologies/keystone). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2020-12692 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-12692 being exploited in the wild.

**How severe is CVE-2020-12692?** Low severity, with a CVSS score of 3.1, published 7 May 2020.

**Which products and versions are affected?** keystone (PyPI) ECOSYSTEM:introduced=0,fixed=15.0.1, ECOSYSTEM:introduced=16.0.0.0rc1,fixed=16.0.0.

**Is there a fix for CVE-2020-12692?** Yes. keystone (PyPI): upgrade to 15.0.1, 16.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-12692?** Check whether you run keystone (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- keystone (PyPI): upgrade to 15.0.1, 16.0.0 or later

  ```sh
  pip install "keystone>=16.0.0"
  ```


## Affected products

- keystone (PyPI) ECOSYSTEM:introduced=0,fixed=15.0.1, ECOSYSTEM:introduced=16.0.0.0rc1,fixed=16.0.0

## Identifiers

- CVE-2020-12692
- GHSA-rqw2-hhrf-7936
- PYSEC-2020-56

## Related threats

- [PYSEC-2026-2549 - OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials](https://junglewise.ai/threats/cve-2015-7546-openstack-identity-keystone-and-keystonemiddleware-insufficiently)
- [PYSEC-2026-830 - OpenStack Keystone allows information disclosure during account locking](https://junglewise.ai/threats/cve-2021-38155-openstack-keystone-allows-information-disclosure-during-account)
- [PYSEC-2026-831 - OpenStack Identity Keystone Privilege Escalation vulnerability](https://junglewise.ai/threats/cve-2013-4477-openstack-identity-keystone-privilege-escalation-vulnerability)
- [PYSEC-2026-833 - OpenStack Keystone does not invalidate existing tokens when granting or revoking roles](https://junglewise.ai/threats/cve-2012-4413-openstack-keystone-does-not-invalidate-existing-tokens-when)
- [PYSEC-2026-832 - OpenStack Keystone Improper Authentication vulnerability](https://junglewise.ai/threats/cve-2012-4456-openstack-keystone-improper-authentication-vulnerability)