CVE-2015-1852: Insecure Certification Verification in python-keystoneclient

python-keystoneclient Updated 02 Oct 2025

Summary

17/04/2015
Yes i
Unrated
Not published

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 python-keystoneclient versions < 1.4.0. Fixed in 1.4.0. How to fix ↓

Also tracked for

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.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

python-keystoneclient is a Python library that provides a client interface for the OpenStack Identity API. It allows users to authenticate and interact with the OpenStack Identity service. The s3_token middleware in OpenStack keystonemiddleware and python-keystoneclient versions prior to 1.6.0 and 1.4.0 respectively, are vulnerable to a security issue that disables certification verification when the 'insecure' option is set in a paste configuration file (paste.ini), regardless of the value. This vulnerability can be exploited by remote attackers to conduct man-in-the-middle attacks using a crafted certificate.

Vulnerability Detail

The vulnerability (CVE-2015-1852) in python-keystoneclient allows an attacker to bypass certification verification when the 'insecure' option is set in the paste configuration file. This means that even if the 'insecure' option is set to 'False', the certification verification will still be disabled. As a result, an attacker can present a crafted certificate during the SSL/TLS handshake, tricking the client into establishing a connection with the attacker's server. This enables the attacker to intercept and modify the communication between the client and the server, potentially leading to unauthorized access, data leakage, or other malicious activities.

How To Fix

Latest published version: 6.0.0 as of 23 Oct 2026

pip install --upgrade "python-keystoneclient==6.0.0"

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.4.0

This is the first release that contains the fix.

pip install --upgrade "python-keystoneclient==1.4.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

The vulnerability in python-keystoneclient versions prior to 1.4.0 allows for insecure certification verification, potentially enabling man-in-the-middle attacks. To mitigate this vulnerability, it is crucial to upgrade to python-keystoneclient version 1.4.0 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for python-keystoneclient →

Share this vulnerability

FAQ

This vulnerability allows remote attackers to conduct man-in-the-middle attacks by disabling certification verification. It can lead to unauthorized access, data leakage, and potential manipulation of communication between the client and the server.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the Pipfile.lock file.

Yes, upgrading python-keystoneclient to version 1.4.0 or later will fix this vulnerability. It is recommended to update your installation to the latest version.

There are no known public exploits available for this vulnerability at the time of writing. However, it is important to apply the fix as soon as possible to prevent potential attacks.

You can find more information about this vulnerability in the advisory database of the Python Package Index (PyPI) at the following source: https://github.com/pypa/advisory-database/blob/main/vulns/python-keystoneclient/PYSEC-2015-31.yaml

Related vulnerabilities

Recent vulnerabilities recorded for python-keystoneclient.

How To Fix

Latest published version: 6.0.0 as of 23 Oct 2026

pip install --upgrade "python-keystoneclient==6.0.0"

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.4.0

This is the first release that contains the fix.

pip install --upgrade "python-keystoneclient==1.4.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback