Vulnerability Database · PyPI · python-keystoneclient · Version

python-keystoneclient 0.2.3

0.2.3 is affected by 16 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 6.0.0.

Critical 2 High 1 Medium 4 Low 2 Unrated 7

Released 18 Mar 2013 Licence non-standard Also known from other sources 18 Newer releases 99 Database updated 23/Oct/2026

Release and licence data published by PyPI. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

python-keystoneclient 0.2.3 vulnerabilities

16 vulnerabilities cover python-keystoneclient 0.2.3. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2013-2166: Inadequate Encryption Strength in python-keystoneclient 9.8 critical 0.3.0 12 Oct 2021
CVE-2013-2167: Insufficient Verification of Data Authenticity in python-keystoneclient 9.8 critical 0.3.0 10 Mar 2020
CVE-2013-2104: python-keystoneclient Token Expiry Check Bypass 7.5 high 0.2.4 17 May 2022
CVE-2014-0105: python-keystoneclient context confusion in Keystone auth_token middleware 6.0 low 0.7.0 17 May 2022
CVE-2013-2255: python-keystoneclient - Improper Certificate Validation Vulnerability 5.9 medium 0.4.0 09 Jul 2026
Improper Certificate Validation in OpenStack Keystone and Other Components 5.9 medium 0.4.0 05 May 2022
CVE-2013-2030: python-keystoneclient - Insecure Temporary Directory in OpenStack Nova 4.3 medium 0.2.4 06 Jul 2026
CVE-2013-2030: Insecure Temporary Directory in OpenStack Nova Keystone Middleware 4.3 medium 0.2.4 17 May 2022
CVE-2013-2013: python-keystoneclient unsecure user password update 2.9 low 0.2.4 17 May 2022
CVE-2013-2167: python-keystoneclient memcache signing bypass N/A unrated 0.3.0 10 Dec 2019
CVE-2013-2166: python-keystoneclient Memcache Encryption Bypass N/A unrated 0.3.0 10 Dec 2019
CVE-2015-1852: Insecure Certification Verification in python-keystoneclient N/A unrated 1.4.0 17 Apr 2015
CVE-2014-7144: OpenStack keystonemiddleware Insecure Certificate Verification N/A unrated 0.11.0 02 Oct 2014
CVE-2014-0105: OpenStack Python Keystoneclient Auth Token Middleware Privilege Escalation N/A unrated 0.7.0 15 Apr 2014
CVE-2013-2104: python-keystoneclient Token Expiry Check Bypass N/A unrated 0.2.4 21 Jan 2014
CVE-2013-2013: python-keystoneclient User Password Update Command Local Information Disclosure N/A unrated 0.2.4 01 Oct 2013

Looking for another version, or everything Vulert holds for python-keystoneclient?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About python-keystoneclient 0.2.3

Is python-keystoneclient 0.2.3 vulnerable?

Yes. 16 vulnerabilities in the Vulert database cover python-keystoneclient 0.2.3: 2 critical, 1 high, 4 medium and 2 low, plus 7 not yet rated. The upgrade Vulert recommends is 6.0.0, and each entry above names the fixed version to move to.

Which version of python-keystoneclient should I use instead of 0.2.3?

6.0.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.2.3 the latest release of python-keystoneclient?

No. 0.2.3 was published 18 Mar 2013, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor python-keystoneclient for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the python-keystoneclient version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.