dbcve.org
Secret ServerApplication · Thycotic

CVE-2019-18355

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-23
Fix available
A fix is available. Upgrade to 10.7.000000 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An SSRF issue was discovered in the legacy Web launcher in Thycotic Secret Server before 10.7.

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 confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the legacy Web launcher component of Thycotic Secret Server versions prior to 10.7. This flaw allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services or exfiltrating data.

MitigationUpgrade Thycotic Secret Server to version 10.7 or later. Additionally, restrict network access to the Secret Server and implement network segmentation to limit the impact of any SSRF exploitation.

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
Secret ServerApplication
Affected:< 10.7.000000

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Secret Server version
    Access the Secret Server admin interface and navigate to the About or Configuration section to view the exact version number, or check the installation files and release documentation for the deployed version
    Affected if The version displayed is less than 10.7.000000 (for example, 10.6.x, 10.5.x, or earlier)
  2. Identify legacy Web launcher configuration
    In the Secret Server admin panel, locate the Web launcher settings under the Launcher or Configuration menu options. Check whether the legacy Web launcher option is enabled or selected as the default launcher type
    Affected if The legacy Web launcher component is enabled or configured as the primary launcher method
  3. Verify Web launcher endpoint accessibility
    Review Secret Server logs and web server access logs for requests to the Web launcher endpoint. Examine the launcher configuration files or database settings that control the Web launcher behavior
    Affected if The legacy Web launcher endpoint is exposed and accessible to users
  4. Audit network outbound connections
    Monitor network traffic or review firewall logs for outbound HTTP/HTTPS connections originating from the Secret Server to internal IP ranges or unexpected external destinations, particularly connections initiated by the launcher component
    Affected if The server is making arbitrary HTTP requests to internal resources or unexpected external addresses that were not configured by administrators

The environment is affected if Secret Server version is below 10.7.000000 and the legacy Web launcher component is enabled or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 10.7.000000 or later
Fixed in 10.7.000000
Interim mitigation

Upgrade Thycotic Secret Server to version 10.7 or later. Additionally, restrict network access to the Secret Server and implement network segmentation to limit the impact of any SSRF exploitation.

Recommended fix Moderate confidence

Secret Server 10.7.000000 or later

  1. Back up your Secret Server database and configuration files before proceeding with any upgrade
  2. Download Secret Server version 10.7.000000 or later from the official Thycotic download portal
  3. Review Thycotic's upgrade documentation for version 10.7 to understand any prerequisites
  4. Run the Secret Server upgrade installer on your production server
  5. After upgrade completion, verify the legacy Web launcher is no longer in use or has been updated
  6. Confirm Secret Server is running at version 10.7 or later via the About section in the admin console
  7. Test that secret retrieval and launch functionality works correctly post-upgrade
Caveat Review Thycotic release notes for version 10.7 to check for any configuration or feature changes that may impact your environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secret Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18355 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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