Vulnerability Note VU#477960

WeOnlyDo! Software wodSSHServer ActiveX component fails to properly validate key exchange algorithm strings

Original Release date: 18 May 2006 | Last revised: 18 May 2006


The WeOnlyDo! Software wodSSHServer ActiveX component fails to properly validate the length of key exchange algorithm strings. This may allow a remote, unauthenticated attacker to execute arbitrary code.


wodSSHServer ActiveX component

According to the wodSSHServer ActiveX component website:

    wodSSHServer is an SSH Server ActiveX component (but also Telnet Server ActiveX as well) that will give you ability to easily add SSH2 (and SFTP) server capabilities to your application, as well as old TELNET server protocol.
The Problem

wodSSHServer does not validate key exchange algorithm strings supplied by a client. If a client sends a specially crafted key exchange algorithm string to a vulnerable wodSSHServer installation, that attacker may be able to trigger the overflow.

Any application that uses the wodSSHServer ActiveX Component may be affected by this vulnerability. Known instances of this are freeSSHd and freeFTPd, but there may be others.

Note that working exploit code for this vulnerability is publicly available.


A remote attacker may be able to execute arbitrary code on the server using the wodSSHServer ActiveX component. If that server is running with administrative privileges, the attacker could gain complete control of the system.



This issue is addressed in wodSSHServer ActiveX component version 1.3.4, freeSSHd version 1.0.10, and freeFTPd version 1.0.11.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
WeOnlyDo! SoftwareAffected-18 May 2006
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



This issue was reported by Gerry Eisenhaur.

This document was written by Jeff Gennari.

Other Information

  • CVE IDs: CVE-2006-2407
  • Date Public: 12 May 2006
  • Date First Published: 18 May 2006
  • Date Last Updated: 18 May 2006
  • Severity Metric: 32.92
  • Document Revision: 28


If you have feedback, comments, or additional information about this vulnerability, please send us email.