# CVE-2016-6655: Command injection in Cloud Foundry

> A malicious user can execute arbitrary commands on Cloud Foundry servers via a command injection flaw in a common script.

- **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:** 13 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4rmm-hmcx-2hg3

## What is CVE-2016-6655?

CVE-2016-6655 is a critical command injection vulnerability in Cloud Foundry, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Cloud Foundry Foundation Cloud Foundry release versions prior to v245 and cf-mysql-release versions prior to v31. A command injection vulnerability was discovered in a common script used by many Cloud Foundry components. A malicious user may exploit numerous vectors to execute arbitrary commands on servers running Cloud Foundry.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 2 products.


Products: Cloudfoundry Cf-Mysql-Release, Cloudfoundry Cf-Release.

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

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

## Is CVE-2016-6655 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6655 is a critical command injection vulnerability in Cloud Foundry, published on 13 Jun 2017. 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-6655 in the wild and no public exploit code.

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

## Sources

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

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