# CVE-2016-8631: Business logic in Openshift Enterprise

> An attacker with route creation access can overwrite existing routes to redirect network traffic, compromising data confidentiality and integrity.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 31 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-973m-857j-grqw, RHSA-2016:2696

## What is CVE-2016-8631?

CVE-2016-8631 is a medium-severity vulnerability in Redhat Openshift, published on 31 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The OpenShift Enterprise 3 router does not properly sort routes when processing newly added routes. An attacker with access to create routes can potentially overwrite existing routes and redirect network traffic for other users to their own site.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `atomic-openshift` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-clients` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-clients-redistributable` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-dockerregistry` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-master` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-node` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-pod` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-sdn-ovs` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `atomic-openshift-tests` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| `tuned-profiles-atomic-openshift-node` | Red Hat:openshift:3.3::el7 | All versions | 0:3.3.1.4-1.git.0.7c8657c.el7 |

Products: Redhat Openshift.

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

Apply the vendor's patch.

## Is CVE-2016-8631 being exploited?

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

## Other vulnerabilities in Redhat Openshift

- [CVE-2014-3496](https://insights.sbomify.com/CVE-2014-3496/): Command injection in n/a (critical 10.0)
- [CVE-2014-0234](https://insights.sbomify.com/CVE-2014-0234/): Hardcoded credentials in Red Hat OpenShift Enterprise (critical 9.8)
- [CVE-2013-2060](https://insights.sbomify.com/CVE-2013-2060/): Command injection in OpenShift Origin (critical 9.8)
- [CVE-2013-4561](https://insights.sbomify.com/CVE-2013-4561/): Path traversal in openshift-origin-msg-node-mcollective (critical 9.1)
- [CVE-2014-0163](https://insights.sbomify.com/CVE-2014-0163/): Command injection in Openshift (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8631 is a medium-severity vulnerability in Redhat Openshift, published on 31 Jul 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-8631 in the wild and no public exploit code.

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

## Sources

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

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