CVE-2013-2167

Description

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

Link	Tags
https://security-tracker.debian.org/tracker/CVE-2013-2167	third party advisory
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2167	issue tracking third party advisory patch
https://access.redhat.com/security/cve/cve-2013-2167	third party advisory
https://bugs.gentoo.org/show_bug.cgi?id=CVE-2013-2167	not applicable
http://lists.fedoraproject.org/pipermail/package-announce/2013-August/113944.html	third party advisory release notes
http://rhn.redhat.com/errata/RHSA-2013-0992.html	third party advisory
http://www.openwall.com/lists/oss-security/2013/06/19/5	third party advisory mailing list
http://www.securityfocus.com/bid/60680	vdb entry third party advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/85492	vdb entry third party advisory

What is the severity of CVE-2013-2167?: CVE-2013-2167 has been scored as a critical severity vulnerability.
How to fix CVE-2013-2167?: To fix CVE-2013-2167, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2013-2167 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2013-2167 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2013-2167?: CVE-2013-2167 affects python-keystoneclient python-keystoneclient.