dbcve.org
Secret ServerApplication · Thycotic

CVE-2021-41845

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-01
Fix available
A fix is available. Upgrade to 11.0.000007 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A SQL injection issue was discovered in ThycoticCentrify Secret Server before 11.0.000007. The only affected versions are 10.9.000032 through 11.0.000006.

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 confidence

SQL injection vulnerability in ThycoticCentrify Secret Server (versions 10.9.000032 through 11.0.000006) allows an authenticated attacker to manipulate database queries through unsanitized input, potentially exposing or exfiltrating sensitive secrets stored in the system.

MitigationUpgrade Secret Server to version 11.0.000007 or later to patch the SQL injection vulnerability.

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.9.000032, < 11.0.000007

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify Secret Server installation
    Locate the Thycotic Secret Server or ThycoticCentrify Secret Server web application in your environment. Check the application name displayed in the web UI header or login page.
    Affected if The application is not Secret Server or ThycoticCentrify Secret Server
  2. Determine installed version number
    Access the Secret Server About page (typically found in the Help or Administration menu) or check the version displayed on the login page. Compare the version to the affected range.
    Affected if The installed version is 10.9.000032 through 11.0.000006 inclusive, or any version between 10.9.000032 and 11.0.000006 (not including 11.0.000007)
  3. Verify authentication is enabled
    Confirm that user authentication is configured and enabled in Secret Server. Check if local users, AD integration, or other authentication providers are active.
    Affected if Authentication is enabled and user accounts exist (the SQL injection requires an authenticated session to exploit)
  4. Identify exposed SQL injection entry points
    Review Secret Server configuration for any custom reports, advanced searches, or API endpoints that accept user input and query the database. These are potential vectors for the unsanitized input.
    Affected if Custom reports, searches, or API endpoints that accept user input are configured and accessible to authenticated users

You are affected if Secret Server or ThycoticCentrify Secret Server is installed with a version between 10.9.000032 and 11.0.000006 inclusive and authenticated users can access input fields that query the database.

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 11.0.000007 or later
Fixed in 11.0.000007
Interim mitigation

Upgrade Secret Server to version 11.0.000007 or later to patch the SQL injection vulnerability.

Recommended fix High confidence

11.0.000007 or later

  1. 1. Check the current version of Secret Server by navigating to Admin > Configuration or using the About section in the UI
  2. 2. Confirm the installed version is between 10.9.000032 and 11.0.000006 (inclusive), which are the affected versions
  3. 3. Review ThycoticCentrify Secret Server upgrade prerequisites in the official documentation
  4. 4. Perform a full backup of the Secret Server database and configuration files before upgrading
  5. 5. Upgrade Secret Server to version 11.0.000007 or later
  6. 6. After upgrade, verify the new version is displayed correctly in the Admin > Configuration > About page
  7. 7. Test critical workflows (secret retrieval, search, authentication) to confirm the upgrade was successful and the application functions properly

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-41845 — 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-2021-41845 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