# CVE-2015-5271: TripleO Heat templates might allow remote attackers to obtain sensitive information from private containers

> Attackers can access private container data in OpenStack Swift when staticweb middleware is enabled due to incorrect service ordering in TripleO Heat templates.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8936-44gw-7664, PYSEC-2016-34, RHSA-2015:1862

## What is CVE-2015-5271?

CVE-2015-5271 is a high-severity vulnerability in Redhat Openstack, published on 15 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TripleO Heat templates (tripleo-heat-templates) do not properly order the Identity Service (keystone) before the OpenStack Object Storage (Swift) staticweb middleware in the swiftproxy pipeline when the staticweb middleware is enabled, which might allow remote attackers to obtain sensitive information from private containers via unspecified vectors.

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

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

3 open source packages ship an affected version, including tripleo-heat-templates. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.7 |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.7 |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.7 |
| `ahc-tools` | Red Hat:openstack-director:7::el7 | All versions | 0:0.1.1-6.el7ost |
| `instack-undercloud` | Red Hat:openstack-director:7::el7 | All versions | 0:2.1.2-29.el7ost |
| `openstack-ironic-discoverd` | Red Hat:openstack-director:7::el7 | All versions | 0:1.1.0-6.el7ost |
| `openstack-ironic-discoverd-ramdisk` | Red Hat:openstack-director:7::el7 | All versions | 0:1.1.0-6.el7ost |
| `openstack-tripleo-common` | Red Hat:openstack-director:7::el7 | All versions | 0:0.0.1.dev6-3.git49b57eb.el7ost |
| `openstack-tripleo-heat-templates` | Red Hat:openstack-director:7::el7 | All versions | 0:0.8.6-71.el7ost |
| `openstack-tripleo-image-elements` | Red Hat:openstack-director:7::el7 | All versions | 0:0.9.6-10.el7ost |
| `openstack-tripleo-puppet-elements` | Red Hat:openstack-director:7::el7 | All versions | 0:0.0.1-5.el7ost |
| `openstack-tuskar` | Red Hat:openstack-director:7::el7 | All versions | 0:0.4.18-4.el7ost |
| `openstack-tuskar-ui` | Red Hat:openstack-director:7::el7 | All versions | 0:0.4.0-3.el7ost |
| `os-cloud-config` | Red Hat:openstack-director:7::el7 | All versions | 0:0.2.8-7.el7ost |
| `os-net-config` | Red Hat:openstack-director:7::el7 | All versions | 0:0.1.4-4.el7ost |
| `python-hardware` | Red Hat:openstack-director:7::el7 | All versions | 0:0.14-7.el7ost |
| `python-hardware-doc` | Red Hat:openstack-director:7::el7 | All versions | 0:0.14-7.el7ost |
| `python-ironic-discoverd` | Red Hat:openstack-director:7::el7 | All versions | 0:1.1.0-6.el7ost |
| `python-proliantutils` | Red Hat:openstack-director:7::el7 | All versions | 0:2.1.0-4.el7ost |
| `python-rdomanager-oscplugin` | Red Hat:openstack-director:7::el7 | All versions | 0:0.0.10-8.el7ost |

Products: Openstack Tripleo Heat Templates, Redhat Openstack.

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

Upgrade tripleo-heat-templates to 0.8.7 or later.

## Is CVE-2015-5271 being exploited?

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

## Other vulnerabilities in Redhat Openstack

- [CVE-2018-10898](https://insights.sbomify.com/CVE-2018-10898/): Hardcoded credentials in openstack-tripleo-heat-templates (high 8.8)
- [CVE-2015-5303](https://insights.sbomify.com/CVE-2015-5303/): OpenStack TripleO Heat templates spoof metadata requests (high 7.5)
- [CVE-2021-3585](https://insights.sbomify.com/CVE-2021-3585/): Information disclosure in openstack/tripleo-heat-templates. (medium 5.5)
- [CVE-2021-4180](https://insights.sbomify.com/CVE-2021-4180/): Exposure of Sensitive Information to an Unauthorized Actor in OpenStack tripleo-heat-templates (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5271 is a high-severity vulnerability in Redhat Openstack, published on 15 Apr 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-5271 in the wild and no public exploit code.

Affected packages and fixed versions:
- tripleo-heat-templates (PyPI): affected all versions; fixed in 0.8.7
- tripleo-heat-templates (PyPI): affected all versions; fixed in 0.8.7
- tripleo-heat-templates (PyPI): affected all versions; fixed in 0.8.7

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

## Sources

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

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