Title: S3Token TLS cert verification option not honored Reporter: Brant Knudson (IBM) Products: keystonemiddleware, python-keystoneclient Affects: versions through 1.5.0 (keystonemiddleware), versions through 1.3.0 (python-keystoneclient) Description: Brant Knudson from IBM reported a vulnerability in keystonemiddleware (formerly shipped as python-keystoneclient). When the 'insecure' option is set in a S3Token paste configuration file its value is effectively ignored and instead assumed to be true. As a result certificate verification will be disabled, leaving TLS connections open to MITM attacks. Note that it's unusual to explicitly add this option and then set it to false, so the impact of this bug is thought to be limited. All versions of s3_token middleware with TLS settings configured are affected by this flaw. I've backported the patch to 1.0.0 so we can do a fast stablization. arches, please do so (x86 and amd64). Reproducible: Always
to be clear, stabilize dev-python/python-keystoneclient-1.0.0-r1
Arches, please test and mark stable: =dev-python/python-keystoneclient-1.0.0-r1 Target Keywords : "amd64 x86" Thank you!
bad versions removed 1.0.0-r1 and >=1.3.0-r2 have the fix
Arches and Maintainer(s), Thank you for your work. GLSA Vote: Yes
GLSA vote: no.
GLSA Vote: No, closing noglsa
CVE-2015-1852 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1852): The s3_token middleware in OpenStack keystonemiddleware before 1.6.0 and python-keystoneclient before 1.4.0 disables certification verification when the "insecure" option is set in a paste configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate, a different vulnerability than CVE-2014-7144.