# CVE-2015-1852: OpenStack keystonemiddleware and python-keystoneclient vulnerable to man-in-the-middle attacks

Source: https://junglewise.ai/threats/cve-2015-1852-openstack-keystonemiddleware-and-python-keystoneclient-vulnerable  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2015-04-17  
License: CC BY 4.0 with a link back

CVE-2015-1852 · Severity: low · CVSS 3.1 · Published 2015-04-17

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

Technologies: [keystonemiddleware (PyPI)](https://junglewise.ai/threats/technologies/pypi-keystonemiddleware), [python-keystoneclient (PyPI)](https://junglewise.ai/threats/technologies/python-keystoneclient). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2015-1852 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2015-1852 being exploited in the wild.

**How severe is CVE-2015-1852?** Low severity, with a CVSS score of 3.1, published 17 April 2015.

**Which products and versions are affected?** keystonemiddleware (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.0; python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.0.

**Is there a fix for CVE-2015-1852?** Yes. keystonemiddleware (PyPI): upgrade to 1.6.0 or later; python-keystoneclient (PyPI): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2015-1852?** Check whether you run keystonemiddleware (PyPI) or python-keystoneclient (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- keystonemiddleware (PyPI): upgrade to 1.6.0 or later

  ```sh
  pip install "keystonemiddleware>=1.6.0"
  ```

- python-keystoneclient (PyPI): upgrade to 1.4.0 or later

  ```sh
  pip install "python-keystoneclient>=1.4.0"
  ```


## Affected products

- keystonemiddleware (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.0
- python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.0

## Identifiers

- CVE-2015-1852
- GHSA-p9wq-mjh8-q72m
- PYSEC-2015-30
- PYSEC-2015-31

## Related threats

- [PYSEC-2026-2549 - OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials](https://junglewise.ai/threats/cve-2015-7546-openstack-identity-keystone-and-keystonemiddleware-insufficiently)
- [PYSEC-2026-911 - OpenStack Nova uses insecure keystone middleware tmpdir by default](https://junglewise.ai/threats/cve-2013-2030-openstack-nova-uses-insecure-keystone-middleware-tmpdir-by-default)
- [PYSEC-2026-656 - OpenStack Keystone and other components vulnerable to Improper Certificate Validation](https://junglewise.ai/threats/cve-2013-2255-openstack-keystone-and-other-components-vulnerable-to-improper)
- [PYSEC-2019-161 - python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass](https://junglewise.ai/threats/cve-2013-2167-insufficient-verification-of-data-authenticity-in-python)
- [PYSEC-2019-197 - python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass](https://junglewise.ai/threats/cve-2013-2166-inadequate-encryption-strength-in-python-keystoneclient)