How severe is CVE-2013-2255?

CVE-2013-2255 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2013-2255?

CVE-2013-2255 affects the following packages: python-keystoneclient (PyPI), cinder (PyPI), neutron (PyPI), keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-2255?

Update python-keystoneclient to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2255 is resolved across your whole dependency graph.

How do I detect CVE-2013-2255 in my PyPI dependencies?

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

How do I mitigate CVE-2013-2255 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-2013-2255 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-2255 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-2013-2255?

CVE-2013-2255 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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-2013-2255?

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

When was CVE-2013-2255 published, and has it been updated?

CVE-2013-2255 was published on November 1, 2019 and was last updated on July 13, 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

MEDIUM severity

CVE-2013-2255 — python-keystoneclient

MEDIUMFix: openstack/cinder@0f9652d

CVE-2013-2255 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in python-keystoneclient. A fix is available for python-keystoneclient — see the affected versions and patch details below.

OpenStack Keystone and other components vulnerable to Improper Certificate Validation

Also known asGHSA-qh2x-hpf9-cf2gPYSEC-2026-2413PYSEC-2026-2677PYSEC-2026-3034PYSEC-2026-656

Published

Nov 1, 2019

Updated

Jul 13, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% 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

4 pkgs affected

🐍python-keystoneclient🐍cinder🐍neutron🐍keystone

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

HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side SSL certificates.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`python-keystoneclient`	all versions	0.4.0`pip install --upgrade 'python-keystoneclient==0.4.0'`
🐍PyPI	`cinder`	all versions	7.0.0a0`pip install --upgrade 'cinder==7.0.0a0'`
🐍PyPI	`neutron`	all versions	7.0.0a0`pip install --upgrade 'neutron==7.0.0a0'`
🐍PyPI	`keystone`	all versions	8.0.0a0`pip install --upgrade 'keystone==8.0.0a0'`

Affected Products

4 products · 7 configurations

debian linuxdebian

3 versions

8.09.010.0

Application

computeopenstack

1 version

2013.1

Application

keystoneopenstack

1 version

2013

Application

openstackredhat

2 versions

3.04.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-keystoneclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update python-keystoneclient to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2255 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.

Frequently Asked Questions

HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side SSL certificates.

O3 Security · Impact-Aware SCA

Is CVE-2013-2255 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

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

CWE Classification

CWE-295CWE-295

Weaponization

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

OpenSSF Scorecard

Package health score

cinder

3.5/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Nov 1, 2019

Last updated

Jul 13, 2026

Identifiers

CVE-2013-2255

GHSA-qh2x-hpf9-cf2g

PYSEC-2026-2413

PYSEC-2026-2677

PYSEC-2026-3034

References

Advisoryaccess.redhat.com · cve 2013 2255 Advisorybugs.launchpad.net Advisorybugzilla.redhat.com · show bug.cgi Advisorybugzilla.suse.com · show bug.cgi Advisoryexchange.xforce.ibmcloud.com Advisorysecurity-tracker.debian.org · CVE 2013 2255 Advisorysecurityfocus.com Advisorynvd.nist.gov · CVE 2013 2255 Webgithub.com · 0f9652d92e175a1f7dc3c2a37ab444b8f189375a Webgithub.com · 5bd4c2984d329625a2a8442b316fa235dbb88a3d Webgithub.com · 7255e056092f034daaeb4246a812900645d46911 Webgithub.com · 20e166fd8a943ee3f91ba362a47e9c14c7cc5f4c Webweb.archive.org

Related vulnerabilities

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

CVE-2013-2104CVE-2014-7144CVE-2013-2013CVE-2014-0105CVE-2015-1852CVE-2013-2030CVE-2013-2166CVE-2013-2167

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 13, 2026

CVE-2013-2255 — python-keystoneclient

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

Frequently Asked Questions

Is CVE-2013-2255 in your dependencies?