# CVE-2017-4975: Misconfiguration in PCF Tile Generator

> The PCF Tile Generator creates tiles with open security groups that override operator settings, allowing unauthorized network access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 13 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g4x5-pp86-35wg

## What is CVE-2017-4975?

CVE-2017-4975 is a high-severity vulnerability in PCF Tile Generator, 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 Pivotal PCF Tile Generator versions prior to 6.0.0. Tiles created by the PCF Tile Generator create a running open security group that overrides security groups set by the operator.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Pivotal Pcf Tile Generator.

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

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

## Is CVE-2017-4975 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-4975 is a high-severity vulnerability in PCF Tile Generator, 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-2017-4975 in the wild and no public exploit code.

Affected product: PCF Tile Generator. 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-4975/ (Markdown: https://insights.sbomify.com/CVE-2017-4975/index.md)
```

## Sources

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

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