# CVE-2016-9223: Misconfiguration in Cisco CloudCenter Orchestrator

> Unauthenticated attackers can install high-privilege Docker containers if the Docker Engine TCP port is exposed on all interfaces.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r7qm-f8h2-jq46

## What is CVE-2016-9223?

CVE-2016-9223 is a critical vulnerability in Cisco CloudCenter Orchestrator, published on 26 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Docker Engine configuration of Cisco CloudCenter Orchestrator (CCO; formerly CliQr) could allow an unauthenticated, remote attacker to install Docker containers with high privileges on the affected system. Affected Products: This vulnerability affect all releases of Cisco CloudCenter Orchestrator (CCO) deployments where the Docker Engine TCP port 2375 is open on the system and bound to local address 0.0.0.0 (any interface).

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Cloudcenter Orchestrator.

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

No fix has been published for CVE-2016-9223 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-9223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9223 is a critical vulnerability in Cisco CloudCenter Orchestrator, published on 26 Dec 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-2016-9223 in the wild and no public exploit code.

Affected product: Cisco CloudCenter Orchestrator. 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-9223/ (Markdown: https://insights.sbomify.com/CVE-2016-9223/index.md)
```

## Sources

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

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