Single Sign On For Pivotal Cloud FoundryApplication · VMware
CVE-2017-8044
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 Pivotal Single Sign-On for PCF (1.3.x versions prior to 1.3.4 and 1.4.x versions prior to 1.4.3), certain pages allow code to be injected into the DOM environment through query parameters, leading to XSS attacks.
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 confidenceThis is a DOM-based XSS vulnerability in Pivotal Single Sign-On for PCF where certain pages fail to properly sanitize query parameters, allowing attackers to inject malicious scripts into the DOM environment that execute in users' browsers.
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
Single Sign On For Pivotal Cloud FoundryApplication
= 1.3.0= 1.3.2= 1.3.3= 1.4.1= 1.4.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate the installed version of VMware Single Sign-On for PCFAccess the Pivotal Cloud Foundry Ops Manager, navigate to the VMware Single Sign-On tile, and check the version number displayed in the product tile details or stemcell informationAffected if The version shown matches exactly 1.3.0, 1.3.2, 1.3.3, 1.4.1, or 1.4.2
-
Verify the SSO login UI is exposedAccess the Pivotal SSO login page URL (typically at /login or the custom domain configured for SSO) and attempt to append arbitrary query parameters such as ?test=<script>alert(1)</script> to the URLAffected if The page renders user-controlled query parameters directly into the HTML without sanitization, causing the script to execute or appear in the page source
-
Check for custom domain configurationReview the Pivotal SSO tile configuration in Ops Manager to identify the configured authentication domain and any custom login page URLs that accept user-supplied query parametersAffected if Custom login domains or redirect URIs are configured and accept unsanitized query strings that get reflected in the response
-
Identify accessible endpoints handling query parametersExamine the network traffic or logs when accessing SSO pages with various query parameters; check if parameters like 'redirect', 'state', or custom parameters are reflected in the DOMAffected if Query parameters from the URL are directly embedded into the page response without output encoding
A user is affected if the installed VMware Single Sign-On for PCF version matches exactly 1.3.0, 1.3.2, 1.3.3, 1.4.1, or 1.4.2 AND the web-based login interface is accessible and reflects query parameters without sanitization.
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 Pivotal SSO to version 1.3.4 or later (1.3.x) or 1.4.3 or later (1.4.x), and implement proper input validation and output encoding on all query parameters in affected pages.
Fix this in Single Sign On For Pivotal Cloud Foundry
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8044 — 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-8044 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