VanDyke Software

VanDyke Software products do not use Java and do not use the Apache Log4j library.

The Log4j vulnerability is not applicable to VanDyke Software products.

CVE-2014-7169
US-CERT TA14-268A

The GNU Bourne-Again Shell (Bash) 'Shellshock' vulnerability is not applicable to VShell. VShell does not set the environment variable necessary for the exploit to be possible.

Impact of the OpenSSL Heartbleed Vulnerability on SecureCRT, SecureFX, and the VanDyke ClientPack

CVE-2014-0160

VShell FTPS and the OpenSSL Heartbleed Vulnerability

CVE-2014-0160

Dual_EC_DRBG and Extended Random (ER) algorithms not used in VanDyke Software products.

CPNI has released a security advisory describing a vulnerability in SSH that allows an attacker with control over the network to recover up to 32 bits of plaintext from an SSH-protected connection in the standard configuration. VShell® version 3.5.1 and earlier, SecureCRT® version 6.1.2 and earlier, SecureFX® version 6.1.2 and earlier, and VanDyke ClientPack 6.1.2 and earlier are potentially vulnerable to this attack.

Debian has released a security advisory describing a vulnerability in the random number generator used by the OpenSSL package included with the Debian GNU/Linux, Ubuntu, and other Debain-based operating systems.

Not Applicable to VanDyke Software products. However, it is recommended that you upgrade your Debian- and Ubuntu-based systems and then regenerate cryptographic key material as described in the advisory.

It is theoretically possible for an attacker to forge RSA signatures when the RSA key has a public exponent of three. SecureCRT^® version 5.2.1 and earlier, SecureFX^® version 4.0.1 and earlier, and VShell^® version 2.6.2 and earlier for Windows, Red Hat Linux, HP-UX, AIX, and Solaris are potentially vulnerable to this attack.

In SecureCRT versions 5.0 through 5.0.4 and SecureFX versions 3.0 through 3.0.4, a buffer overflow was theoretically possible when a Unicode string was converted to a narrow string.

In VShell versions 2.3.5 and earlier for Windows, when a host key is automatically created by VShell, the host key file inherits the permissions of its parent directory, potentially allowing access to authenticated users.

VShell version 2.3.6 will ensure that when a host key is automatically generated, the permissions on the host key file will be set such that only SYSTEM and members of the Administrators group will have access rights.

SecureCRT is reported prone to a remote denial of service vulnerability. It is reported that supplying an excessive string value to the application through the hostname field may trigger this vulnerability. Apparently, this causes the client application to crash.

SecureCRT 4.0.9 and earlier may be vulnerable when SSH2 is used. SecureCRT 4.1 or newer provides a fix for SSH2 connections.

Secunia Advisory - SecureCRT Arbitrary Configuration Folder Specification Vulnerability. CRT™ and SecureCRT 4.0 and 4.1 allow an arbitrary configuration folder to be specified to the "telnet:" URI handler via the "/F" command-line option. Successful exploitation allows execution of arbitrary commands via a malicious logon script with the privileges of the user running CRT or SecureCRT. This vulnerability is only applicable to users who have made CRT or SecureCRT their default Telnet client.

CERT Vulnerability Note - Remote denial-of-service vulnerability in the KDC and libraries.

Not Applicable to VanDyke Software Products. CERT has released a security advisory affecting MIT Kerberos 5 versions 1.3.4 and earlier. Although VanDyke products are not affected, there may be installations of VShell within an MIT Kerberos 5 environment which support Kerberos authentications through GSSAPI. In such cases, administrators are strongly encouraged to update MIT Kerberos to a version later than 1.3.4.

Microsoft MS04-007

US-CERT
TA-04-041A

Microsoft has released a security bulletin (MS04-007) describing a vulnerability in the parsing of ASN.1 data that could result in remote code execution.

US-CERT published an advisory on this vulnerability on February 10, 2004.

Not Applicable to VanDyke Software products. It is, however, a critical vulnerability in affected versions of Windows for which Microsoft updates should be applied immediately.

View Details

CERT Vulnerability Note - Multiple vulnerabilities in SSL/TLS implementations

Not Applicable to VanDyke Software products. This vulnerability only affects products that use OpenSSL.

CERT Vulnerability Note - A vulnerability in the OpenSSH daemon (sshd) may give remote attackers a better chance of gaining access to restricted resources.

CERT Vulnerability Note - Timing Attack Vulnerabilities
"Cryptographic libraries and applications do not adequately defend against timing attacks." SecureCRT 4.0.4 and earlier may be vulnerable when SSH1 is used. SSH2 connections are not affected by the vulnerability. No other VanDyke Software product is affected by this vulnerability. SecureCRT 4.0.9 or newer provides a fix for SSH1 connections.

View Details

VanDyke Software released versions of it's client applications to eliminate a security issue that made login credentials transmitted by VanDyke secure clients vulnerable to discovery if an attacker were able to access memory or a memory dump on the local machine.

View Details

VanDyke Software released SecureCRT version 3.4.8 and version SecureCRT 4.0.9 or newer to eliminate a security issue in SecureCRT 2.x, 3.x, 4.0 beta 2 or earlier. The issue made SecureCRT vulnerable to a buffer overflow attack which could allow malicious parties to execute arbitrary code when connecting to an SSH1 server that has been modified to perform this exploit. SSH2 connections are not affected by the vulnerability.

View Details

CERT Advisory CA-2002-36 Regarding SSH Vulnerabilities