Skip to content

python-keystoneclient vulnerable to context confusion in Keystone auth_token middleware

Moderate severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Aug 3, 2023

Package

pip python-keystoneclient (pip)

Affected versions

<= 0.6.0

Patched versions

0.7.0

Description

A context confusion vulnerability was identified in Keystone auth_token middleware (shipped in python-keystoneclient) before 0.7.0. By doing repeated requests, with sufficient load on the target system, an authenticated user may in certain situations assume another authenticated user's complete identity and multi-tenant authorizations, potentially resulting in a privilege escalation. Note that it is related to a bad interaction between eventlet and python-memcached that should be avoided if the calling process already monkey-patches "thread" to use eventlet. Only keystone middleware setups using auth_token with memcache are vulnerable.

References

Published by the National Vulnerability Database Apr 15, 2014
Published to the GitHub Advisory Database May 17, 2022
Reviewed Aug 3, 2023
Last updated Aug 3, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L

EPSS score

0.332%
(71st percentile)

Weaknesses

CVE ID

CVE-2014-0105

GHSA ID

GHSA-gwvq-rgqf-993f

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.