CVE-2017-4975
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 · uneditedAn 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.
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 confidenceThe PCF Tile Generator versions prior to 6.0.0 create tiles that automatically deploy an open security group which overrides any security group rules explicitly configured by operators. This can inadvertently expose internal services to untrusted network access, as the tile-generated security group takes precedence over operator-defined rules.
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<= 5.0.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify PCF Tile Generator versionLocate the PCF Tile Generator installation or build environment and check the installed version (typically via 'tile-generator --version' or checking the product configuration file)Affected if Version is 5.0.7 or lower (any version <= 5.0.7)
-
Identify tiles generated by PCF Tile GeneratorReview your PCF deployment to identify tiles that were created using the PCF Tile Generator tool; check tile metadata or deployment manifests for the tile originAffected if Any tile in the deployment was generated using the vulnerable PCF Tile Generator version
-
Inspect deployed security group configurationRun 'cf security-groups' or access the PCF Ops Manager security group settings to list all security groups; examine the security group rules associated with each tileAffected if A security group exists with overly permissive rules (0.0.0.0/0 or wide internal network access) that was not explicitly configured by the operator
-
Verify security group precedenceCheck PCF documentation or run 'cf security-groups' to review which security groups are bound to which spaces/stages; identify if any tile-generated security group is taking precedence over operator-defined rulesAffected if A security group created by the tile is overriding or superseding operator-configured security group rules
You are affected if PCF Tile Generator version 5.0.7 or lower was used to create and deploy any tile, and an open security group from that tile is overriding your explicitly configured rules.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade PCF Tile Generator to version 6.0.0 or later, then regenerate and redeploy all affected tiles to replace insecure configurations with properly scoped security group settings that respect operator-defined rules.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-4975 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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