CVE-2018-1267
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 · uneditedCloud Foundry Silk CNI plugin, versions prior to 0.2.0, contains an improper access control vulnerability. If the platform is configured with an application security group (ASG) that overlaps with the Silk overlay network, any applications can reach any other application on the network regardless of the configured routing policies.
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 Silk CNI plugin in Cloud Foundry prior to version 0.2.0 contains an improper access control flaw where Application Security Groups (ASGs) configured to overlap with the Silk overlay network are bypassed, allowing any application to communicate with any other application on the overlay network regardless of intended routing policies.
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< 0.2.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine Silk Release versionQuery the deployed BOSH releases in your Cloud Foundry environment and identify the Silk Release version. This can typically be done via 'bosh releases' or through the Ops Manager UI if used for deployment.Affected if The Silk Release version is less than 0.2.0.
-
Identify the Silk overlay network rangeExamine your Cloud Foundry deployment manifest or network configuration to determine the CIDR range assigned to the Silk overlay network. Look for the network configuration specifically designated for container-to-container networking.Affected if You cannot determine the overlay network range or no overlay network is configured (but the vulnerability may not apply in the latter case).
-
Review Application Security Group configurationsUse the CF CLI command 'cf security-groups' to list all configured ASGs, then inspect each ASG's rules using 'cf security-group <group-name>' to see the defined CIDR ranges and ports.Affected if Any ASG includes a CIDR range that overlaps with or contains the Silk overlay network range.
-
Check for ASG assignments to spaces or orgsUse 'cf spaces' to identify spaces, then check which ASGs are applied to those spaces via 'cf bind-security-group' or the org/space security group bindings in your CF deployment.Affected if ASGs with overlapping ranges are bound to spaces or orgs, meaning the bypass could affect traffic in those scopes.
You are affected if your Silk Release version is below 0.2.0 AND you have Application Security Groups configured with CIDR ranges that overlap with the Silk overlay network, allowing potential unauthorized container-to-container communication.
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 data0.2.0
Upgrade the Silk CNI plugin to version 0.2.0 or later to remediate the access control bypass, and verify that ASG configurations do not overlap with the Silk overlay network range.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1267 — 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-2018-1267 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