CVE-2020-12691: OpenStack Keystone V3 /credentials endpoint policy logic allows to change credentials owner or target project ID

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

An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.

Technologies: keystone (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-12691 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-12691 being exploited in the wild.
How severe is CVE-2020-12691?
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.
Is there a fix for CVE-2020-12691?
Yes. keystone (PyPI): upgrade to 15.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-12691?
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 or later
    pip install "keystone>=15.0.1"

Affected products

  • keystone (PyPI) ECOSYSTEM:introduced=0,fixed=15.0.1

Identifiers

  • CVE-2020-12691
  • GHSA-4427-7f3w-mqv6
  • PYSEC-2020-55

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