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
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2020-10755 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
cinder🐍cinder🐍cinder🐍os-brick🐍os-brick🐍os-brickReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | cinder | ≥ 14.0.0&&< 14.1.0 | 14.1.0pip install --upgrade 'cinder==14.1.0' |
| 🐍PyPI | cinder | ≥ 15.0.0&&< 15.2.0 | 15.2.0pip install --upgrade 'cinder==15.2.0' |
| 🐍PyPI | cinder | ≥ 16.0.0&&< 16.1.0 | 16.1.0pip install --upgrade 'cinder==16.1.0' |
| 🐍PyPI | os-brick | ≥ 2.8.0&&< 2.8.6 | 2.8.6pip install --upgrade 'os-brick==2.8.6' |
| 🐍PyPI | os-brick | ≥ 2.10.0&&< 2.10.4 | 2.10.4pip install --upgrade 'os-brick==2.10.4' |
| 🐍PyPI | os-brick | ≥ 3.0.0&&< 3.0.2 | 3.0.2pip install --upgrade 'os-brick==3.0.2' |
Detection & mitigation playbook
Open-source dependencyDetect
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-10755 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2020-10755. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
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.
| 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
Is CVE-2020-10755 in your dependencies?
O3 Security finds CVE-2020-10755 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.