First published: Tue Apr 07 2015(Updated: )
A vulnerability was discovered in OpenStack: Title: S3Token TLS cert verification option not honored Reporter: Brant Knudson (IBM) Products: keystonemiddleware, python-keystoneclient Affects: versions up to 1.5.0 (keystonemiddleware), versions up to 0.11.2 (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. Acknowledgements: Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brant Knudson from IBM as the original reporter.
Affected Software | Affected Version | How to fix |
---|---|---|
OpenStack keystonemiddleware | <1.5.0 | |
OpenStack Keystone | <0.11.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1209527 is considered moderate due to potential risks related to TLS certificate verification.
To fix REDHAT-BUG-1209527, upgrade the OpenStack keystonemiddleware to version 1.5.1 or later, and python-keystoneclient to version 0.11.3 or later.
REDHAT-BUG-1209527 affects OpenStack keystonemiddleware versions up to 1.5.0 and python-keystoneclient versions up to 0.11.2.
REDHAT-BUG-1209527 was reported by Brant Knudson from IBM.
REDHAT-BUG-1209527 addresses the failure of S3Token to honor TLS certificate verification options.