# CVE-2017-15139: Information disclosure in openstack-cinder

> Attackers can read sensitive data from previous tenants due to improper zero-padding in specific ScaleIO volume configurations.

- **Severity:** Medium 5.1 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15139, GHSA-j9j4-4235-xf59, RHSA-2018:3601, RHSA-2019:0917, SUSE-SU-2019:0716-1, UBUNTU-CVE-2017-15139

## What is CVE-2017-15139?

CVE-2017-15139 is a medium-severity vulnerability in Redhat Openstack, published on 27 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in openstack-cinder releases up to and including Queens, allowing newly created volumes in certain storage volume configurations to contain previous data. It specifically affects ScaleIO volumes using thin volumes and zero padding. This could lead to leakage of sensitive information between tenants.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-15139?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-cinder` | Red Hat:openstack:10::el7 | All versions | 1:9.1.4-50.el7ost |
| `python-cinder` | Red Hat:openstack:10::el7 | All versions | 1:9.1.4-50.el7ost |
| `python-cinder-tests` | Red Hat:openstack:10::el7 | All versions | 1:9.1.4-50.el7ost |
| `openstack-cinder` | Red Hat:openstack:13::el7 | All versions | 1:12.0.4-2.el7ost |
| `python-cinder` | Red Hat:openstack:13::el7 | All versions | 1:12.0.4-2.el7ost |
| `openstack-cinder` | SUSE:OpenStack Cloud 7 | All versions | 9.1.5~dev6-4.21.3 |
| `openstack-cinder-doc` | SUSE:OpenStack Cloud 7 | All versions | 9.1.5~dev6-4.21.3 |
| `openstack-horizon-plugin-designate-ui` | SUSE:OpenStack Cloud 7 | All versions | 3.0.2~dev1-3.9.3 |
| `openstack-neutron` | SUSE:OpenStack Cloud 7 | All versions | 9.4.2~dev21-7.27.3 |
| `openstack-neutron-doc` | SUSE:OpenStack Cloud 7 | All versions | 9.4.2~dev21-7.27.3 |
| `openstack-neutron-lbaas` | SUSE:OpenStack Cloud 7 | All versions | 9.2.2~dev11-4.15.3 |
| `openstack-neutron-lbaas-doc` | SUSE:OpenStack Cloud 7 | All versions | 9.2.2~dev11-4.15.3 |

Products: Openstack Cinder, Redhat Openstack.

## How do I fix CVE-2017-15139?

Apply the vendor's patch.

## Is CVE-2017-15139 being exploited?

There is no known exploitation of CVE-2017-15139 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Openstack

- [CVE-2015-5162](https://insights.sbomify.com/CVE-2015-5162/): OpenStack Cinder, Glance, and Nova contain Uncontrolled Resource Consumption (high 7.5)
- [CVE-2024-32498](https://insights.sbomify.com/CVE-2024-32498/): OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access (medium 6.5)
- [CVE-2014-3641](https://insights.sbomify.com/CVE-2014-3641/): OpenStack Cinder Exposure of Sensitive Information to an Unauthorized Actor vulnerability (medium 4.0)
- [CVE-2014-7231](https://insights.sbomify.com/CVE-2014-7231/): OpenStack Oslo utility sensitive information exposure via log files (low 2.1)
- [CVE-2013-4183](https://insights.sbomify.com/CVE-2013-4183/): OpenStack Cinder LVMVolumeDriver does not zero deleted snapshots (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15139 and fix it if it is affected.

What it is: CVE-2017-15139 is a medium-severity vulnerability in Redhat Openstack, published on 27 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15139 in the wild and no public exploit code.

Affected product: Redhat Openstack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-15139/ (Markdown: https://insights.sbomify.com/CVE-2017-15139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15139
- OSV: https://osv.dev/vulnerability/CVE-2017-15139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15139/
Summaries are generated and may contain mistakes; the official description above is the record.