# CVE-2016-9599: Missing authorization in puppet-tripleo

> A flaw in Puppet TripleO allowed creating firewall rules with empty ports, enabling unauthorized access to resources when SSL is enabled.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:** 23 Apr 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f29f-jrc4-qmh5, RHSA-2017:0025

## What is CVE-2016-9599?

CVE-2016-9599 is a high-severity missing authorization vulnerability in Redhat Openstack, published on 23 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

puppet-tripleo before versions 5.5.0, 6.2.0 is vulnerable to an access-control flaw in the IPtables rules management, which allowed the creation of TCP/UDP rules with empty port values. If SSL is enabled, a malicious user could use these open ports to gain access to unauthorized resources.

Weakness: CWE-284 (Improper Access Control)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `puppet-tripleo` | Red Hat:openstack:10::el7 | All versions | 0:5.4.0-4.el7ost |

Products: Openstack Puppet-Tripleo, Redhat Openstack.

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

Upgrade to a fixed version.

## Is CVE-2016-9599 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9599 is a high-severity missing authorization vulnerability in Redhat Openstack, published on 23 Apr 2018. 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-9599 in the wild and no public exploit code.

Affected product: Redhat Openstack. 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-9599/ (Markdown: https://insights.sbomify.com/CVE-2016-9599/index.md)
```

## Sources

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

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