# CVE-2016-9185: Server-side request forgery in n/a

> An authenticated user can exploit Server-Side Request Forgery in OpenStack Heat to reveal internal network configuration details.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 4 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-9185, GHSA-249h-g975-9xj2, RHSA-2017:1450, RHSA-2017:1456

## What is CVE-2016-9185?

CVE-2016-9185 is a medium-severity server-side request forgery vulnerability in n/a, published on 4 Nov 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Heat, by launching a new Heat stack with a local URL an authenticated user may conduct network discovery revealing internal network configuration. Affected versions are <=5.0.3, >=6.0.0 <=6.1.0, and ==7.0.0.

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

## Which versions are affected by CVE-2016-9185?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-heat` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat-api` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat-api-cfn` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat-api-cloudwatch` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat-common` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat-engine` | Red Hat:openstack:7::el7 | All versions | 0:2015.1.4-3.el7ost |
| `openstack-heat` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |
| `openstack-heat-api` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |
| `openstack-heat-api-cfn` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |
| `openstack-heat-api-cloudwatch` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |
| `openstack-heat-common` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |
| `openstack-heat-engine` | Red Hat:openstack:8::el7 | All versions | 1:5.0.3-2.el7ost |

Products: Openstack Heat.

## How do I fix CVE-2016-9185?

Apply the vendor's patch.

## Is CVE-2016-9185 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-1625](https://insights.sbomify.com/CVE-2023-1625/): Information leak in api (high 7.4)
- [CVE-2017-2621](https://insights.sbomify.com/CVE-2017-2621/): Information disclosure in openstack-heat (medium 5.9)
- [CVE-2024-7319](https://insights.sbomify.com/CVE-2024-7319/): Openstack-heat: incomplete fix for cve-2023-1625 (medium 5.0)
- [CVE-2013-6426](https://insights.sbomify.com/CVE-2013-6426/): Missing authorization in n/a (medium 4.0)
- [CVE-2013-6428](https://insights.sbomify.com/CVE-2013-6428/): Auth bypass in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9185 and fix it if it is affected.

What it is: CVE-2016-9185 is a medium-severity server-side request forgery vulnerability in n/a, published on 4 Nov 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-9185 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-2016-9185/ (Markdown: https://insights.sbomify.com/CVE-2016-9185/index.md)
```

## Sources

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

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