How severe is CVE-2020-10755?

CVE-2020-10755 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-10755?

CVE-2020-10755 affects the following packages: cinder (PyPI), cinder (PyPI), cinder (PyPI), os-brick (PyPI), os-brick (PyPI), os-brick (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2020-10755?

Update cinder to 14.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10755 is resolved across your whole dependency graph.

How do I detect CVE-2020-10755 in my PyPI dependencies?

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

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

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

CVE-2020-10755 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th 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-2020-10755?

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

When was CVE-2020-10755 published, and has it been updated?

CVE-2020-10755 was published on June 10, 2020 and was last updated on July 7, 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-2020-10755 — cinder

MEDIUMFix: openstack/cinder@ba785ee

CVE-2020-10755 is a medium-severity (CVSS 6.5) CWE-522 vulnerability in cinder. A fix is available for cinder — see the affected versions and patch details below.

Openstack cinder Improper handling of ScaleIO backend credentials

Also known asGHSA-v3m2-pg96-w33mPYSEC-2020-228PYSEC-2026-891

Published

Jun 10, 2020

Updated

Jul 7, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

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

6 pkgs affected

🐍cinder🐍cinder🐍cinder🐍os-brick🐍os-brick🐍os-brick

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

An insecure-credentials flaw was found in all openstack-cinder versions before openstack-cinder 14.1.0, all openstack-cinder 15.x.x versions before openstack-cinder 15.2.0 and all openstack-cinder 16.x.x versions before openstack-cinder 16.1.0. When using openstack-cinder with the Dell EMC ScaleIO or VxFlex OS backend storage driver, credentials for the entire backend are exposed in the connection_info element in all Block Storage v3 Attachments API calls containing that element. This flaw enables an end-user to create a volume, make an API call to show the attachment detail information, and retrieve a username and password that may be used to connect to another user's volume. Additionally, these credentials are valid for the ScaleIO or VxFlex OS Management API, should an attacker discover the Management API endpoint. Source: OpenStack project

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cinder`	≥ 14.0.0&&< 14.1.0	14.1.0`pip install --upgrade 'cinder==14.1.0'`
🐍PyPI	`cinder`	≥ 15.0.0&&< 15.2.0	15.2.0`pip install --upgrade 'cinder==15.2.0'`
🐍PyPI	`cinder`	≥ 16.0.0&&< 16.1.0	16.1.0`pip install --upgrade 'cinder==16.1.0'`
🐍PyPI	`os-brick`	≥ 2.8.0&&< 2.8.6	2.8.6`pip install --upgrade 'os-brick==2.8.6'`
🐍PyPI	`os-brick`	≥ 2.10.0&&< 2.10.4	2.10.4`pip install --upgrade 'os-brick==2.10.4'`
🐍PyPI	`os-brick`	≥ 3.0.0&&< 3.0.2	3.0.2`pip install --upgrade 'os-brick==3.0.2'`

Affected Products

2 products · 5 configurations

ubuntu linuxcanonical

2 versions

18.0420.04

Application

openstack-cinderredhat

≥ 16.0.0 && < 16.1.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 cinder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cinder to 14.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10755 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

In addition to the software updates for this flaw, you must deploy a new configuration file on compute nodes, cinder nodes, and anywhere you would perform a volume attachment in your deployment. For detailed information, refer to referenced article.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2020-10755 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenStack Platform 13.0 (Queens)	`openstack-cinder-1:12.0.10-19.el7ost`	RHSA-2020:4391
Red Hat OpenStack Platform 16.1	`openstack-cinder-1:15.3.1-1.20200914173114.00ac80b.el8ost`	RHSA-2020:4283

Frequently Asked Questions

An insecure-credentials flaw was found in all openstack-cinder versions before openstack-cinder 14.1.0, all openstack-cinder 15.x.x versions before openstack-cinder 15.2.0 and all openstack-cinder 16.x.x versions before openstack-cinder 16.1.0. When using openstack-cinder with the Dell EMC ScaleIO or VxFlex OS backend storage driver, credentials for the entire backend are exposed in the ``connection_info`` element in all Block Storage v3 Attachments API calls containing that element. This flaw enables an end-user to create a volume, make an API call to show the attachment detail information, a

O3 Security · Impact-Aware SCA

Is CVE-2020-10755 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-522CWE-522

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

Jun 10, 2020

Last updated

Jul 7, 2026

Identifiers

CVE-2020-10755

GHSA-v3m2-pg96-w33m

PYSEC-2020-228

PYSEC-2026-891

References

Advisoryusn.ubuntu.com · 4420 1 Advisorywiki.openstack.org · OSSN 0086 Advisorynvd.nist.gov · CVE 2020 10755 Reportbugzilla.redhat.com · show bug.cgi Webgithub.com · ba785eef5f515b869c0d68016e84bb74f76ab45e Webgithub.com · 4047948f1ac8055a025972ad73ec3ec421450775 Webbugs.launchpad.net Webgithub.com · PYSEC 2020 228.yaml Webusn.ubuntu.com · 4420 1

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting cinder are rated as high or higher (top: high).

CVE-2024-32498CVE-2022-47951CVE-2015-1851CVE-2013-4183CVE-2014-3641CVE-2015-5162CVE-2013-4202CVE-2013-2255

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 7, 2026

CVE-2020-10755 — cinder

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-2020-10755 in your dependencies?