SyncopeApplication · Apache
CVE-2019-17557
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 · uneditedIt was found that the Apache Syncope EndUser UI login page prio to 2.0.15 and 2.1.6 reflects the successMessage parameters. By this mean, a user accessing the Enduser UI could execute javascript code from URL query string.
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 confidenceApache Syncope EndUser UI versions prior to 2.0.15 and 2.1.6 contain a reflected XSS vulnerability in the login page where the successMessage URL parameter is reflected back to the user without proper output encoding, allowing injection of arbitrary JavaScript code via the query string.
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
SyncopeApplication
>= 2.0.0, < 2.0.15>= 2.1.0, < 2.1.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Apache Syncope EndUser UI deploymentCheck your application server (Tomcat, Jetty, etc.) for the deployed Syncope EndUser WAR file. Common locations include the webapps directory. The WAR file is typically named something like 'syncope-enduser.war' or contains 'enduser' in the filename.Affected if The EndUser UI WAR file is not found - the component is not deployed
-
Determine the installed EndUser UI versionExamine the WAR file name for the version number (e.g., syncope-enduser-2.0.14.war). If not in the filename, extract the WAR and check the pom.xml file inside, or look for a version.properties or similar file in the WEB-INF/classes directory.Affected if The version cannot be determined or is not visible in the deployment artifacts
-
Compare your version against the affected rangesCheck if your installed version falls within >= 2.0.0 and < 2.0.15, OR >= 2.1.0 and < 2.1.6. If the version is 2.0.15 or higher, or 2.1.6 or higher, it is NOT affected.Affected if Your version is 2.0.0 through 2.0.14, or 2.1.0 through 2.1.5
-
Verify the EndUser login endpoint is accessibleAttempt to access the EndUser login page URL (typically at /syncope-enduser/login or /enduser/login). If the application responds with a login page, the vulnerable component is exposed.Affected if The login page is accessible via HTTP/HTTPS and responds successfully
You are affected if the Apache Syncope EndUser UI is deployed and accessible, and its version falls between 2.0.0-2.0.14 or 2.1.0-2.1.5.
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 data2.0.152.1.6
Upgrade to Apache Syncope EndUser UI version 2.0.15 or 2.1.6 or later, which includes proper output encoding for the successMessage parameter. As a temporary workaround, avoid clicking untrusted links containing successMessage parameters.
Fix this in Syncope
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17557 — 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-2019-17557 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