# CVE-2017-14390: Misconfiguration in cf-deployment cf-deployment v0.35.0

> Misconfiguration in Cloud Foundry Loggregator allows logs to be drained to unintended locations, potentially exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g54m-6fph-847q

## What is CVE-2017-14390?

CVE-2017-14390 is a high-severity vulnerability in cf-deployment cf-deployment v0.35.0, published on 27 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Cloud Foundry Foundation cf-deployment v0.35.0, a misconfiguration with Loggregator and syslog-drain causes logs to be drained to unintended locations.

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

It affects 1 product.


Products: Pivotal Software Cf-Deployment.

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

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

## Is CVE-2017-14390 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14390 is a high-severity vulnerability in cf-deployment cf-deployment v0.35.0, published on 27 Nov 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-2017-14390 in the wild and no public exploit code.

Affected product: cf-deployment cf-deployment v0.35.0. 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-14390/ (Markdown: https://insights.sbomify.com/CVE-2017-14390/index.md)
```

## Sources

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

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