CVE-2017-4963
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 Cloud Foundry Foundation Cloud Foundry release v252 and earlier versions, UAA stand-alone release v2.0.0 - v2.7.4.12 & v3.0.0 - v3.11.0, and UAA bosh release v26 & earlier versions. UAA is vulnerable to session fixation when configured to authenticate against external SAML or OpenID Connect based identity providers.
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 confidenceUAA (User Account and Authentication) in Cloud Foundry contains a session fixation vulnerability when configured to authenticate against external SAML or OpenID Connect identity providers. The issue allows attackers to potentially hijack user sessions by setting or fixing session IDs before the legitimate user authenticates, exploiting the lack of session ID regeneration after external IdP authentication completes.
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<= 252>= 2.0.0, <= 2.7.4.12>= 3.0.0, <= 3.11.0<= 26CVSS 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.0/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 installed UAA versionQuery the UAA server version endpoint or check the release manifest file for the deployed UAA release versionAffected if The version is <= 2.7.4.12 for 2.x line, or <= 3.11.0 for 3.x line, or Cf Release <= 252, or UAA Release <= 26
-
Identify external identity provider configurationReview UAA configuration files (typically in the deployment manifest or uaac configuration) for SAML service provider or OpenID Connect provider definitionsAffected if UAA is configured to delegate authentication to external SAML or OIDC identity providers
-
Verify session ID regeneration behaviorInspect the UAA authentication flow logs or perform a test authentication via an external IdP and observe whether the session ID changes after the IdP authentication completesAffected if Session ID remains unchanged before and after external IdP authentication (session fixation vulnerability present)
-
Check UAA deployment manifest for version referencesLocate the deployment manifest for the Cloud Foundry environment and search for UAA release version numbersAffected if The manifest shows UAA release version <= 26 or Cf Release version <= 252
A user is affected if their UAA version falls within the vulnerable ranges AND they have configured external SAML or OIDC identity providers for authentication.
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 UAA to version v2.7.4.13 or later for the 2.x line, or v3.12.0 or later for the 3.x line to receive the session regeneration fix. Alternatively, monitor authentication flows closely and implement additional session monitoring for users authenticating via external SAML/OIDC providers.
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4963 — 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-4963 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