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

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). 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
    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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.