Tectia ClientApplication · Ssh

CVE-2021-27892

HIGH · 7.8 CVSS v3.1 Published 2021-03-15
Fix available
A fix is available. Upgrade to 6.4.19 or later.
See remediation →
80/100
Remediation priority · High
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
SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation. ConnectSecure on Windows is affected.

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

This is a local privilege escalation vulnerability in SSH Tectia Client and Server (and ConnectSecure) on Windows operating systems, affecting versions prior to 6.4.19. The vulnerability allows a local attacker to gain elevated privileges on the affected Windows system.

MitigationUpgrade SSH Tectia Client and Server (or ConnectSecure) to version 6.4.19 or later on all affected Windows systems.

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
Tectia ClientApplication
Affected:< 6.4.19
Tectia ConnectsecureApplication
Affected:all versions
Tectia ServerApplication
Affected:< 6.4.19

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify SSH Tectia is installed on Windows
    Check for SSH Tectia installation by reviewing installed programs in Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or checking for SSH Tectia executables in Program Files directories
    Affected if SSH Tectia Client, Server, or ConnectSecure is found installed on the Windows system
  2. Identify the installed SSH Tectia product and version
    Locate the version information in the Windows Registry under HKLM\SOFTWARE\SSH Tectia\ or check the version of the main executable (typically sshg3.exe or similar) via right-click Properties > Details
    Affected if Unable to determine version or version is below 6.4.19 for Client/Server, or any version for ConnectSecure
  3. Confirm the product type
    Determine whether the installed product is SSH Tectia Client, Server, or ConnectSecure by reviewing the product name in the installation or registry entry
    Affected if Product is identified as ConnectSecure (all versions affected) or Client/Server version is less than 6.4.19

The environment is affected if SSH Tectia Client or Server version is below 6.4.19, or ConnectSecure of any version, is installed on a Windows system.

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.

From vendor data
Upgrade available Upgrade to 6.4.19 or later
Fixed in 6.4.19
Interim mitigation

Upgrade SSH Tectia Client and Server (or ConnectSecure) to version 6.4.19 or later on all affected Windows systems.

Fix this in Tectia Client Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27892 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