Critical Vulnerabilities in Dropbear SSH version on Deco

Critical Vulnerabilities in Dropbear SSH version on Deco
Critical Vulnerabilities in Dropbear SSH version on Deco
2020-07-29 01:04:31
Model: Deco M5
Hardware Version: V1
Firmware Version: 1.4.4 Build 20200221 Rel 65392

Nessus Security Scanner complains about the version of Dropbear SSH on the Deco M5s I have installed.  Apparently there are several critical exploits that allow for remote code execution.  I get that from the WAN iptables will block access to SSH, but, that doesn't rule out lateral attacks from the LAN.  Does TP-Link have any plans to upgrade to a version of Dropbear that is not vulnerable?

 

Here are the results of the scan:

 
Description

According to its self-reported version in its banner, Dropbear SSH running on the remote host is prior to 2016.74. It is, therefore, affected by the following vulnerabilities :

- A format string flaw exists due to improper handling of string format specifiers (e.g., %s and %x) in usernames and host arguments. An unauthenticated, remote attacker can exploit this to execute arbitrary code with root privileges. (CVE-2016-7406)

- A flaw exists in dropbearconvert due to improper handling of specially crafted OpenSSH key files. An unauthenticated, remote attacker can exploit this to execute arbitrary code. (CVE-2016-7407)

- A flaw exists in dbclient when handling the -m or -c arguments in scripts. An unauthenticated, remote attacker can exploit this, via a specially crafted script, to execute arbitrary code. (CVE-2016-7408)

- A flaw exists in dbclient or dropbear server if they are compiled with the DEBUG_TRACE option and then run using the -v switch. A local attacker can exploit this to disclose process memory. (CVE-2016-7409)

Solution

Upgrade to Dropbear SSH version 2016.74 or later.

 

Output
  •   Version source    : SSH-2.0-dropbear_2015.67
      Installed version : 2015.67
      Fixed version     : 2016.74
2
2
#1
Options
1 Reply
Re:Critical Vulnerabilities in Dropbear SSH version on Deco
2020-09-28 13:28:52

@mniswonger 

 

I think this is the response they gave about SSH: https://www.tp-link.com/us/support/faq/2462/

0
0
#2
Options