CVE-2014-0105: python-keystoneclient vulnerable to context confusion in Keystone auth_token middleware

CVE-2014-0105 · Severity: low · CVSS 3.1 · Published 2014-04-15

The auth_token middleware in the OpenStack Python client library for Keystone (aka python-keystoneclient) before 0.7.0 does not properly retrieve user tokens from memcache, which allows remote authenticated users to gain privileges in opportunistic circumstances via a large number of requests, related to an "interaction between eventlet and python-memcached."

Technologies: python-keystoneclient (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2014-0105 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2014-0105 being exploited in the wild.
How severe is CVE-2014-0105?
Low severity, with a CVSS score of 3.1, published 15 April 2014.
Which products and versions are affected?
python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=0.7.0.
Is there a fix for CVE-2014-0105?
Yes. python-keystoneclient (PyPI): upgrade to 0.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2014-0105?
Check whether you run python-keystoneclient (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

  • python-keystoneclient (PyPI): upgrade to 0.7.0 or later
    pip install "python-keystoneclient>=0.7.0"

Affected products

  • python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=0.7.0

Identifiers

  • CVE-2014-0105
  • GHSA-gwvq-rgqf-993f
  • PYSEC-2014-70

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