# CVE-2015-8749: OpenStack Nova Potential Xen connection password leak via StorageError

> Attackers can obtain sensitive password information from log files in OpenStack Compute when using the Xen backend.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8749, GHSA-c36r-g737-9qp8, PYSEC-2026-870, UBUNTU-CVE-2015-8749

## What is CVE-2015-8749?

CVE-2015-8749 is a medium-severity vulnerability in n/a, published on 15 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The volume_utils._parse_volume_info function in OpenStack Compute (Nova) before 2015.1.3 (kilo) and 12.0.x before 12.0.1 (liberty) includes the connection_info dictionary in the StorageError message when using the Xen backend, which might allow attackers to obtain sensitive password information by reading log files or other unspecified vectors.

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

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

3 open source packages ship an affected version, including nova. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nova` | PyPI | From 12.0.0 | 12.0.1 |
| `nova` | PyPI | From 12.0.0 | 12.0.1 |
| `nova` | PyPI | From 12.0.0 | 12.0.1 |

Products: Openstack Nova.

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

Upgrade nova to 12.0.1 or later.

## Is CVE-2015-8749 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7214](https://insights.sbomify.com/CVE-2017-7214/): OpenStack Nova logs sensitive context from notification exceptions (critical 9.8)
- [CVE-2017-17051](https://insights.sbomify.com/CVE-2017-17051/): OpenStack Nova DoS by rebuilding the same instance with a new image multiple times (high 8.6)
- [CVE-2020-17376](https://insights.sbomify.com/CVE-2020-17376/): OpenStack Nova Live migration fails to update persistent domain XML (high 8.3)
- [CVE-2017-18191](https://insights.sbomify.com/CVE-2017-18191/): OpenStack Nova Denial of service attack on the compute host (high 7.5)
- [CVE-2015-3280](https://insights.sbomify.com/CVE-2015-3280/): OpenStack Compute (nova) allows remote authenticated users to cause a denial of service (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8749 is a medium-severity vulnerability in n/a, published on 15 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8749 in the wild and no public exploit code.

Affected packages and fixed versions:
- nova (PyPI): affected from 12.0.0; fixed in 12.0.1
- nova (PyPI): affected from 12.0.0; fixed in 12.0.1
- nova (PyPI): affected from 12.0.0; fixed in 12.0.1

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-8749/ (Markdown: https://insights.sbomify.com/CVE-2015-8749/index.md)
```

## Sources

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

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