CVE-2015-1852: High severity Openstack keystonemiddleware vulnerability
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 s3token 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.
Other sources
The s3token 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.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-1852?
CVE-2015-1852 is classified as a moderate severity vulnerability.
How do I fix CVE-2015-1852?
To fix CVE-2015-1852, upgrade python-keystoneclient to version 1.4.0 or later, and keystonemiddleware to version 1.6.0 or later.
Which OpenStack products are affected by CVE-2015-1852?
CVE-2015-1852 affects versions up to 1.5.0 of keystonemiddleware and versions up to 0.11.2 of python-keystoneclient.
What impact does CVE-2015-1852 have on system security?
CVE-2015-1852 can lead to an insecure configuration as the S3Token TLS certificate verification option is not honored.
Who reported CVE-2015-1852?
CVE-2015-1852 was reported by Brant Knudson from IBM.