# CVE-2015-7514: Information disclosure in n/a

> Remote authenticated users can obtain sensitive information because OpenStack Ironic fails to clean disks after use.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7514, GHSA-xh73-4jm2-j7c9

## What is CVE-2015-7514?

CVE-2015-7514 is a medium-severity vulnerability in n/a, published on 7 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Ironic 4.2.0 through 4.2.1 does not "clean" the disk after use, which allows remote authenticated users to obtain sensitive information.

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

## Which versions are affected by CVE-2015-7514?

It affects 1 product.


Products: Openstack Ironic.

## How do I fix CVE-2015-7514?

Apply the vendor's patch.

## Is CVE-2015-7514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-42997](https://insights.sbomify.com/CVE-2026-42997/): OpenStack Ironic has an Incorrect Resource Transfer Between Spheres (high 7.7)
- [CVE-2026-42510](https://insights.sbomify.com/CVE-2026-42510/): OpenStack Ironic is Vulnerable to Inclusion of Functionality from Untrusted Control Sphere (medium 6.6)
- [CVE-2026-48681](https://insights.sbomify.com/CVE-2026-48681/): OpenStack Ironic allows file overwrite via directory traversal during deployment with a crafted ISO image (medium 5.9)
- [CVE-2026-46447](https://insights.sbomify.com/CVE-2026-46447/): OpenStack Ironic allows Boot Script Injection (medium 5.8)
- [CVE-2026-50589](https://insights.sbomify.com/CVE-2026-50589/): OpenStack Ironic: Crafted JSON String to Certain Endpoints on the API or JSON-RPC Service May Result in Service Crash (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7514 and fix it if it is affected.

What it is: CVE-2015-7514 is a medium-severity vulnerability in n/a, published on 7 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7514 in the wild and no public exploit code.

Affected product: n/a. 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-2015-7514/ (Markdown: https://insights.sbomify.com/CVE-2015-7514/index.md)
```

## Sources

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

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