dbcve.org
Cloudcenter OrchestratorApplication · Cisco

CVE-2016-9223

CRITICAL · 9.8 CVSS v3.0 Published 2016-12-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Docker Engine TCP port 2375 (unencrypted daemon) is exposed on all network interfaces (0.0.0.0) instead of being bound to localhost only. This allows unauthenticated remote attackers to connect to the Docker API and deploy privileged containers on the affected system.

MitigationBind Docker daemon only to localhost (127.0.0.1) or enable TLS authentication if remote access is required; alternatively firewall port 2375 to prevent external access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloudcenter OrchestratorApplication
Affected:= 4.4.0= 4.5.0= 4.6.0= 4.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Docker daemon is listening on TCP port 2375
    Run 'ss -tlnp | grep 2375' or 'netstat -tlnp | grep 2375' to see if any service is listening on port 2375
    Affected if Port 2375 is open and listening
  2. Identify the bind address for port 2375
    Examine the output from the previous command - look for the local address column (e.g., 0.0.0.0:2375 or 127.0.0.1:2375)
    Affected if The bind address is 0.0.0.0:2375 (all interfaces) rather than 127.0.0.1:2375 (localhost only)
  3. Review Docker daemon configuration files
    Check /etc/docker/daemon.json for an 'hosts' entry, or inspect systemd service files or init scripts for Docker daemon startup flags (-H or --host)
    Affected if Configuration specifies tcp://0.0.0.0:2375 or similar without restricting to localhost

A system is affected if Docker daemon TCP port 2375 is bound to 0.0.0.0 instead of 127.0.0.1, allowing unauthenticated remote access

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Bind Docker daemon only to localhost (127.0.0.1) or enable TLS authentication if remote access is required; alternatively firewall port 2375 to prevent external access.

Recommended fix High confidence
  1. Modify the Docker daemon configuration to bind to localhost (127.0.0.1) instead of 0.0.0.0. Edit the Docker daemon configuration file (typically /etc/systemd/system/docker.service.d/override.conf or /etc/docker/daemon.json)
  2. Add or modify the -H parameter to bind only to 127.0.0.1:2375 instead of tcp://0.0.0.0:2375
  3. Restart the Docker daemon with 'systemctl daemon-reload' and 'systemctl restart docker'
  4. Verify the Docker daemon is no longer listening on external interfaces using 'netstat -tlnp | grep 2375' or 'ss -tlnp | grep 2375'
  5. Alternatively, enable TLS authentication on the Docker daemon for production environments if remote Docker API access is required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloudcenter Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-9223 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data