OSSA-2015-007: S3Token TLS cert verification option not honored

OSSA-2015-007: S3Token TLS cert verification option not honored


April 14, 2015




  • Python-keystoneclient: versions through 1.3.0

  • Keystonemiddleware: versions through 1.5.0


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.



  • Brant Knudson from IBM (CVE-2015-1852)


  • This fix will be included in keystonemiddleware 1.6.0 release and python- keystoneclient 1.4.0 release.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.