CVE-2017-11725
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 · uneditedThe share function in Thycotic Secret Server before 10.2.000019 mishandles the Back Button, leading to unintended redirections.
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 · moderate confidenceThe share function in Thycotic Secret Server before version 10.2.000019 improperly handles the browser Back Button, allowing unintended URL redirections. This could enable attackers to redirect users to malicious pages or cause confusion in the application workflow.
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<= 10.2.000018CVSS 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.0/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.
-
Identify the installed Thycotic Secret Server versionAccess the Secret Server administration panel, typically via /SecretServer within your deployment, and navigate to the About or Version information section. Alternatively, check the installation directory for version metadata files or the installer package used.Affected if The displayed version number is 10.2.000018 or lower
-
Verify the share function is accessibleLog in to Secret Server as a standard user and confirm the share function is available. Navigate to any secret that has been created and look for a share, share with users, or sharing icon/option in the secret detail view.Affected if The share functionality is present and accessible to users in the web interface
-
Test for back button URL redirection behaviorUsing a browser with developer tools open, use the share function to share a secret, then click the browser Back Button to return to the previous page. Inspect the browser address bar and network traffic for any unexpected redirects to external domains or unintended internal routes.Affected if Clicking the Back Button after using the share function triggers an unexpected redirect to an external site or causes the application to navigate to an unintended page
You are affected if your Secret Server version is 10.2.000018 or lower and users can access the share function, as the back button will improperly redirect users.
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 Thycotic Secret Server to version 10.2.000019 or later to obtain the vendor patch addressing the back button handling vulnerability in the share function.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11725 — 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-11725 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