How severe is CVE-2015-1852?

CVE-2015-1852 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-1852?

CVE-2015-1852 affects the following packages: keystonemiddleware (PyPI), python-keystoneclient (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-1852?

Update keystonemiddleware to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1852 is resolved across your whole dependency graph.

How do I detect CVE-2015-1852 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystonemiddleware, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-1852 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2015-1852 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-1852 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-1852?

CVE-2015-1852 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-1852?

CVE-2015-1852 is classified as CWE-17 (CWE-17). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-1852 published, and has it been updated?

CVE-2015-1852 was published on April 17, 2015 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2015-1852 — keystonemiddleware

HIGH

CVE-2015-1852 is a high-severity (CVSS 7.5) CWE-17 vulnerability in keystonemiddleware. A fix is available for keystonemiddleware — see the affected versions and patch details below.

OpenStack keystonemiddleware and python-keystoneclient vulnerable to man-in-the-middle attacks

Also known asGHSA-p9wq-mjh8-q72mPYSEC-2015-30PYSEC-2015-31

Published

Apr 17, 2015

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍keystonemiddleware🐍python-keystoneclient

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystonemiddleware`	all versions	1.6.0`pip install --upgrade 'keystonemiddleware==1.6.0'`
🐍PyPI	`python-keystoneclient`	all versions	1.4.0`pip install --upgrade 'python-keystoneclient==1.4.0'`

Affected Products

3 products · 4 configurations

ubuntu linuxcanonical

2 versions

14.0415.04

Application

keystonemiddlewareopenstack

≤ 1.5.0

range

Application

python-keystoneclientopenstack

≤ 1.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystonemiddleware, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystonemiddleware to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1852 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`python-keystoneclient-1:0.9.0-6.el6ost`	RHSA-2015:1685
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`python-keystoneclient-1:0.11.1-2.el7ost`	RHSA-2015:1677

Ubuntu

USN-2705-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-1852 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-17CWE-17

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 17, 2015

Last updated

Apr 10, 2026

Identifiers

CVE-2015-1852

GHSA-p9wq-mjh8-q72m

PYSEC-2015-30

PYSEC-2015-31

References

Advisorylists.openstack.org Advisoryrhn.redhat.com · RHSA 2015 1677 Advisoryrhn.redhat.com · RHSA 2015 1685 Advisorysecurityfocus.com Advisoryubuntu.com · USN 2705 1 Advisorynvd.nist.gov · CVE 2015 1852 Weboracle.com · bulletinapr2015 2511959 Webbugs.launchpad.net Webaccess.redhat.com · RHSA 2015:1677 Webaccess.redhat.com · RHSA 2015:1685 Webaccess.redhat.com · CVE 2015 1852 Webbugzilla.redhat.com · show bug.cgi Webgithub.com · PYSEC 2015 30.yaml Webgithub.com · PYSEC 2015 31.yaml Webweb.archive.org

Related vulnerabilities

Also affects keystonemiddleware

This CVE is high severity, in line with the other 2 CVEs affecting keystonemiddleware.

CVE-2014-7144CVE-2015-7546

Also affects python-keystoneclient

This CVE is high severity; 2 of 6 other CVEs affecting python-keystoneclient are rated as high or higher (top: critical).

CVE-2013-2104CVE-2013-2013CVE-2014-0105CVE-2013-2030CVE-2013-2255CVE-2013-2166

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026

CVE-2015-1852 — keystonemiddleware

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2015-1852 in your dependencies?