CVE-2018-1221
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 · uneditedIn cf-deployment before 1.14.0 and routing-release before 0.172.0, the Cloud Foundry Gorouter mishandles WebSocket requests for AWS Application Load Balancers (ALBs) and some other HTTP-aware Load Balancers. A user with developer privileges could use this vulnerability to steal data or cause denial of service.
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 Cloud Foundry Gorouter in cf-deployment and routing-release mishandles WebSocket upgrade requests when deployed behind AWS Application Load Balancers and certain other HTTP-aware load balancers. The vulnerability allows authenticated users with developer privileges to intercept WebSocket connections or cause denial of service by exploiting improper handling of the WebSocket handshake headers.
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< 1.14.0< 0.172.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify cf-deployment versionLocate your deployment manifest file or run 'bosh -d <deployment> manifest' to retrieve the deployment configuration. Search for the cf-deployment release version in the manifest.Affected if The cf-deployment version is listed as less than 1.14.0 or the version field is absent/unavailable indicating an older release.
-
Identify routing-release versionIn the same deployment manifest, locate the routing-release release section or run 'bosh releases' to list installed releases. Note the version of the routing-release release.Affected if The routing-release version is less than 0.172.0 or cannot be determined, indicating an unpatched installation.
-
Verify WebSocket upgrade handling is presentExamine the Gorouter configuration in your deployment manifest for WebSocket upgrade-related settings. Check if the router handles WebSocket upgrade headers (Upgrade and Connection) in the proxy configuration.Affected if WebSocket upgrade handling is configured and the deployment version is below the fixed releases.
-
Confirm load balancer type in front of GorouterReview your infrastructure configuration to identify the load balancer type handling traffic to Gorouter nodes. Look for AWS Application Load Balancer (ALB) or other HTTP-aware load balancers configured in the routing path.Affected if AWS ALB or HTTP-aware load balancers are used in the request path to Gorouter, combined with unpatched software versions.
You are affected if your cf-deployment is below version 1.14.0 or routing-release is below version 0.172.0, and you use an AWS ALB or HTTP-aware load balancer with WebSocket-enabled routes.
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.172.01.14.0
Upgrade cf-deployment to version 1.14.0 or later and routing-release to version 0.172.0 or later to obtain the Gorouter patch that properly handles WebSocket requests with HTTP-aware load balancers.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1221 — 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-1221 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