# CVE-2017-4964: Code injection in Cloud Foundry Foundation BOSH Azure CPI Release v22

> A maliciously crafted stemcell can execute arbitrary code on VMs created by the BOSH Azure CPI director.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4w69-xg22-fccq

## What is CVE-2017-4964?

CVE-2017-4964 is a high-severity code injection vulnerability in Cloud Foundry Foundation BOSH Azure CPI Release v22, published on 6 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cloud Foundry Foundation BOSH Azure CPI v22 could potentially allow a maliciously crafted stemcell to execute arbitrary code on VMs created by the director, aka a "CPI code injection vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2017-4964?

It affects 1 product.


Products: Cloudfoundry Bosh Azure Cpi.

## How do I fix CVE-2017-4964?

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

## Is CVE-2017-4964 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-4964 and fix it if it is affected.

What it is: CVE-2017-4964 is a high-severity code injection vulnerability in Cloud Foundry Foundation BOSH Azure CPI Release v22, published on 6 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-4964 in the wild and no public exploit code.

Affected product: Cloud Foundry Foundation BOSH Azure CPI Release v22. 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-2017-4964/ (Markdown: https://insights.sbomify.com/CVE-2017-4964/index.md)
```

## Sources

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

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