CVE-2015-1852: OpenStack keystonemiddleware s3_token Middleware Insecure Certificate Verification
Summary
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... Affects keystonemiddleware versions < 1.6.0. Fixed in 1.6.0. How to fix ↓
Also tracked for
- python-keystoneclient · Debian:11
- python-keystoneclient · PyPI
The same CVE-2015-1852 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenStack keystonemiddleware is a Python library that provides middleware components for the OpenStack Keystone service. It is used to handle authentication and authorization in OpenStack deployments. The s3_token middleware is responsible for validating Amazon S3 authentication tokens. This vulnerability affects versions prior to 1.6.0 of keystonemiddleware and python-keystoneclient.
Vulnerability Detail
The s3_token middleware in OpenStack keystonemiddleware and python-keystoneclient disables certification verification when the "insecure" option is set in a paste configuration file (paste.ini) regardless of the value. This allows remote attackers to conduct man-in-the-middle attacks by using a crafted certificate. This vulnerability is different from CVE-2014-7144. The lack of certificate verification can lead to unauthorized access, data interception, and potential compromise of the OpenStack deployment.
How To Fix
Latest published version: 13.0.1 as of 22 Oct 2026
pip install --upgrade "keystonemiddleware==13.0.1"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.6.0
This is the first release that contains the fix.
pip install --upgrade "keystonemiddleware==1.6.0"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the latest secure version of keystonemiddleware and python-keystoneclient.
Conclusion
The s3_token middleware in OpenStack keystonemiddleware and python-keystoneclient is vulnerable to man-in-the-middle attacks due to the disabling of certificate verification when the "insecure" option is set. Upgrading to version 1.6.0 or later of the affected packages is recommended to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for keystonemiddleware →
FAQ
This vulnerability allows remote attackers to conduct man-in-the-middle attacks on OpenStack deployments, potentially leading to unauthorized access, data interception, and compromise of the system.
There is no known public exploit for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
No, only versions prior to 1.6.0 of keystonemiddleware and python-keystoneclient are affected. It is recommended to upgrade to the latest secure version to mitigate the vulnerability.
Yes, this vulnerability can be exploited remotely by attackers who can intercept network traffic between the OpenStack deployment and the client.
Yes, upgrading to version 1.6.0 or later of keystonemiddleware and python-keystoneclient fixes this vulnerability by enabling certificate verification even when the "insecure" option is set.
Related vulnerabilities
Recent vulnerabilities recorded for keystonemiddleware.
