Openstack CinderApplication · Redhat

CVE-2020-10755

MEDIUM · 6.5 CVSS v3.1 Published 2020-06-10
Fix available
A fix is available. Upgrade to 14.1.0 / 15.2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Insecure credential exposure in OpenStack Cinder when using Dell EMC ScaleIO or VxFlex OS backend storage drivers. Credentials are exposed in plaintext within the connection_info element in Block Storage v3 Attachments API responses, allowing any authenticated user to retrieve backend management credentials valid for both data and management plane access.

MitigationUpgrade openstack-cinder to version 14.1.0, 15.2.0, or 16.1.0 or later. Additionally, rotate all ScaleIO/VxFlex OS credentials that may have been exposed, as they remain valid for the management API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openstack CinderApplication
Affected:< 14.1.0>= 15.0.0, < 15.2.0>= 16.0.0, < 16.1.0
Ubuntu LinuxOperating system
Affected:= 18.04= 20.04

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenStack Cinder version
    Run 'cinder --version' or query the package: 'rpm -q openstack-cinder' (RHEL) or 'dpkg -l openstack-cinder' (Ubuntu)
    Affected if Version is < 14.1.0 OR >= 15.0.0 AND < 15.2.0 OR >= 16.0.0 AND < 16.1.0
  2. Identify configured storage backends
    Inspect /etc/cinder/cinder.conf and search for 'scaleio' or 'vxflexos' under the [DEFAULT] enabled_backends setting or in any backend section
    Affected if ScaleIO or VxFlex OS backend is listed in enabled_backends
  3. Verify driver configuration exists
    Search cinder.conf for sections starting with '[scaleio]' or '[vxflexos]' containing 'volume_driver' pointing to cinder.volume.drivers.dell_emc.scaleio.ScaleIODriver or cinder.volume.drivers.dell_emc.vxflexos.VxFlexOSDriver
    Affected if Either ScaleIO or VxFlex OS volume driver is configured
  4. Test Block Storage v3 Attachments API for credential exposure
    Use openstack CLI: 'openstack volume attachment show <volume_id>' or query the Cinder API endpoint /v3/{project_id}/attachments/{attachment_id} and inspect the connection_info field
    Affected if The response contains plaintext 'password', 'user_name', 'san_ip', or 'management_ip' fields within the connection_info element

Cinder is vulnerable if the version falls within the affected ranges AND ScaleIO or VxFlex OS backend is configured, allowing any authenticated user to retrieve plaintext credentials via the Attachments API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 14.1.0 / 15.2.0 / 16.1.0 or later
Fixed in 14.1.015.2.016.1.0
Interim mitigation

Upgrade openstack-cinder to version 14.1.0, 15.2.0, or 16.1.0 or later. Additionally, rotate all ScaleIO/VxFlex OS credentials that may have been exposed, as they remain valid for the management API.

Fix this in Openstack Cinder Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10755 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data