Tectia Server

tectia_server

Vendor: Ssh • 12 CVEs

CVEs (12)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2021-27893 1Ssh 3Tectia Client Tectia ConnectsecureTectia Server Jun 17, 2026 Mar 15, 2021 N/A· v4 7.0 HIGH· v3 4.4 MEDIUM· v2 SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation in nonstandard conditions. ConnectSecure on Windows is affected.
CVE-2021-27892 1Ssh 3Tectia Client Tectia ConnectsecureTectia Server Jun 17, 2026 Mar 15, 2021 N/A· v4 7.8 HIGH· v3 4.6 MEDIUM· v2 SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation. ConnectSecure on Windows is affected.
CVE-2021-27891 1Ssh 3Tectia Client Tectia ConnectsecureTectia Server Jun 17, 2026 Mar 15, 2021 N/A· v4 8.8 HIGH· v3 6.5 MEDIUM· v2 SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation. ConnectSecure on Windows is affected.
CVE-2012-5975 1Ssh 1Tectia Server Apr 29, 2026 Dec 4, 2012 N/A· v4 N/A· v3 9.3 HIGH· v2 The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password authentication is enabled,...Show more The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password authentication is enabled, allows remote attackers to bypass authentication via a crafted session involving entry of blank passwords, as demonstrated by a root login session from a modified OpenSSH client with an added input_userauth_passwd_changereq call in sshconnect2.c.Show less
CVE-2008-5161 2Openbsd Ssh 5Openssh Tectia ClientTectia Connector+2 more May 28, 2026 Nov 19, 2008 N/A· v4 3.7 LOW· v3 2.6 LOW· v2 Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux o...Show more Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors.Show less
CVE-2007-5616 1Ssh 2Tectia Client Tectia Server Apr 23, 2026 Jan 9, 2008 N/A· v4 N/A· v3 7.2 HIGH· v2 ssh-signer in SSH Tectia Client and Server 5.x before 5.2.4, and 5.3.x before 5.3.6, on Unix and Linux allows local users to gain privileges via unspecified vectors.
CVE-2007-2063 1Ssh 1Tectia Server Apr 23, 2026 Apr 18, 2007 N/A· v4 N/A· v3 4.4 MEDIUM· v2 SSH Tectia Server for IBM z/OS before 5.4.0 uses insecure world-writable permissions for (1) the server pid file, which allows local users to cause arbitrary processes to be stopped, or (2) when _BPX_BATCH_UMASK is missi...Show more SSH Tectia Server for IBM z/OS before 5.4.0 uses insecure world-writable permissions for (1) the server pid file, which allows local users to cause arbitrary processes to be stopped, or (2) when _BPX_BATCH_UMASK is missing from the environment, creates HFS files with insecure permissions, which allows local users to read or modify these files and have other unknown impact.Show less
CVE-2006-5484 1Ssh 4Tectia Client Tectia ConnectorTectia Manager+1 more Apr 23, 2026 Oct 24, 2006 N/A· v4 N/A· v3 5.0 MEDIUM· v2 SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers t...Show more SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.Show less
CVE-2006-4315 1Ssh 4Tectia Client Tectia ConnectorTectia Manager+1 more Apr 16, 2026 Aug 23, 2006 N/A· v4 N/A· v3 7.2 HIGH· v2 Unquoted Windows search path vulnerability in multiple SSH Tectia products, including Client/Server/Connector 5.0.0 and 5.0.1 and Client/Server before 4.4.5, and Manager 2.12 and earlier, when running on Windows, might a...Show more Unquoted Windows search path vulnerability in multiple SSH Tectia products, including Client/Server/Connector 5.0.0 and 5.0.1 and Client/Server before 4.4.5, and Manager 2.12 and earlier, when running on Windows, might allow local users to gain privileges via a malicious program file under "Program Files" or its subdirectories.Show less
CVE-2005-4310 1Ssh 1Tectia Server Apr 16, 2026 Dec 17, 2005 N/A· v4 N/A· v3 7.5 HIGH· v2 SSH Tectia Server 5.0.0 (A, F, and T), when allowing host-based authentication only, allows users to log in with the wrong credentials.
CVE-2005-2146 1Ssh 1Tectia Server Apr 16, 2026 Jul 5, 2005 N/A· v4 N/A· v3 4.6 MEDIUM· v2 SSH Tectia Server 4.3.1 and earlier, and SSH Secure Shell for Windows Servers, uses insecure permissions when generating the Secure Shell host identification key, which allows local users to access the key and spoof the...Show more SSH Tectia Server 4.3.1 and earlier, and SSH Secure Shell for Windows Servers, uses insecure permissions when generating the Secure Shell host identification key, which allows local users to access the key and spoof the server.Show less
CVE-2003-1120 1Ssh 1Tectia Server Apr 16, 2026 Dec 31, 2003 N/A· v4 N/A· v3 3.7 LOW· v2 Race condition in SSH Tectia Server 4.0.3 and 4.0.4 for Unix, when the password change plugin (ssh-passwd-plugin) is enabled, allows local users to obtain the server's private key.