# CVE-2015-5303: OpenStack TripleO Heat templates spoof metadata requests

> Attackers can spoof OpenStack Networking metadata requests by exploiting the default shared secret in TripleO Heat templates.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 11 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m94p-8942-pm49, PYSEC-2016-35, UBUNTU-CVE-2015-5303

## What is CVE-2015-5303?

CVE-2015-5303 is a high-severity vulnerability in n/a, published on 11 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), when deployed via the commandline interface, allow remote attackers to spoof OpenStack Networking metadata requests by leveraging knowledge of the default value of the NeutronMetadataProxySharedSecret parameter.

Weakness: CWE-254

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.10 |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.10 |
| `tripleo-heat-templates` | PyPI | All versions | 0.8.9 |

Products: Openstack Tripleo Heat Templates.

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

Upgrade tripleo-heat-templates to a fixed version for your release line: 0.8.10 or 0.8.9.

## Is CVE-2015-5303 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10898](https://insights.sbomify.com/CVE-2018-10898/): Hardcoded credentials in openstack-tripleo-heat-templates (high 8.8)
- [CVE-2015-5271](https://insights.sbomify.com/CVE-2015-5271/): TripleO Heat templates might allow remote attackers to obtain sensitive information from private containers (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-5303 and fix it if it is affected.

What it is: CVE-2015-5303 is a high-severity vulnerability in n/a, published on 11 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-5303 in the wild and no public exploit code.

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

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

## Sources

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

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