How severe is CVE-2013-2167?

CVE-2013-2167 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2013-2167?

CVE-2013-2167 affects the following packages: python-keystoneclient (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-2167?

Update python-keystoneclient to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2167 is resolved across your whole dependency graph.

How do I detect CVE-2013-2167 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-keystoneclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2167 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-2167 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-2167 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-2167?

CVE-2013-2167 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-2167?

CVE-2013-2167 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-2167 published, and has it been updated?

CVE-2013-2167 was published on December 10, 2019 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2013-2167 — python-keystoneclient

CRITICALFix: openstack/python-keystoneclient@eeefb78

CVE-2013-2167 is a critical-severity (CVSS 9.8) CWE-345 vulnerability in python-keystoneclient. A fix is available for python-keystoneclient — see the affected versions and patch details below.

Insufficient Verification of Data Authenticity in python-keystoneclient

Also known asGHSA-9vg3-cf92-h2h7PYSEC-2019-161

Published

Dec 10, 2019

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍python-keystoneclient

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`python-keystoneclient`	≥ 0.2.3&&< 0.3.0	0.3.0`pip install --upgrade 'python-keystoneclient==0.3.0'`

Affected Products

3 products · 5 configurations

debian linuxdebian

3 versions

8.09.010.0

Application

python-keystoneclientopenstack

≥ 0.2.3 && ≤ 0.2.5

range

Application

openstackredhat

1 version

3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-keystoneclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update python-keystoneclient to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2167 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
OpenStack 3 for RHEL 6	`python-keystoneclient-1:0.2.3-5.el6ost`	RHSA-2013:0992

Frequently Asked Questions

python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass

O3 Security · Impact-Aware SCA

Is CVE-2013-2167 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works