what you don't know can hurt you

TP-Link Archer C50 Insecure Connections

TP-Link Archer C50 Insecure Connections
Posted Apr 11, 2019
Authored by Harley A.W. Lorenzo

An initial analysis of the TP-Link Archer C50 router shows it accepts logins over HTTP, uses a telnet server, and implements SSH with low-bit DSA and RSA keys.

tags | advisory, web
MD5 | 783e2167c37719febac73e7bd25a53be

TP-Link Archer C50 Insecure Connections

Change Mirror Download
================================================================================
Title: Security Analysis of the TP-Link Archer C50 Router
Version: Archer C50(US)_V2_160801 (latest firmware available)
Product Page: https://www.tp-link.com/us/home-networking/wifi-router/archer-c50/
Published: 2019-04-10 (UTC Time)
Published by: Harley A.W. Lorenzo <hl1998@protonmail.com>
<GPG Key: 0xF6EF23904645BA53>
================================================================================

================
Security Details
================

* The C50 router implements a completely unencrypted HTTP authentication
login handshake on its port 80 HTTP server for administrative tasks
* The C50 router implements a telnet server over Busybox Telnetd
* The C50 router implements an SSH service with on Dropbear 2012.55 with
low-bit DSA and RSA keys (1024 and 1040-bit respecitvely)

===================
Login Sniffing/MITM
===================

Because of C50 router login handshake is completely unencrypted (both over HTTP
and telnet) any attacker with access to the network data sent to the router
can easily acquire the username and password sent in the login.

For example, the following proof of concept regarding HTTP traffic:

1. Set up a valid sniffer and listen for the HTTP traffic sent to the server
2. Login to the server via its webserver
3. Watch for a GET request to its base index with a cookie with the format
Authorization=BASIC {[user]:[pass]}
* Where [user] is replaced with the username and [pass] is
replaced with the password entered
* Where everything in {} is encoded in base64

===
SSH
===

* The SSH server is possibly vulnerable to serveral CVEs regarding Dropbear
* DSA is an deprecated singing algorithm and is better replaced with ECDSA
* Both the DSA and RSA keys are well below the recommended size

================
Additional Notes
================

Beside the HTTP sniffing PoC, these are all preliminary findings, and this
research is an ongoing effort.


Login or Register to add favorites

File Archive:

May 2020

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    May 1st
    14 Files
  • 2
    May 2nd
    3 Files
  • 3
    May 3rd
    1 Files
  • 4
    May 4th
    18 Files
  • 5
    May 5th
    15 Files
  • 6
    May 6th
    21 Files
  • 7
    May 7th
    15 Files
  • 8
    May 8th
    19 Files
  • 9
    May 9th
    1 Files
  • 10
    May 10th
    2 Files
  • 11
    May 11th
    18 Files
  • 12
    May 12th
    39 Files
  • 13
    May 13th
    15 Files
  • 14
    May 14th
    17 Files
  • 15
    May 15th
    17 Files
  • 16
    May 16th
    2 Files
  • 17
    May 17th
    2 Files
  • 18
    May 18th
    15 Files
  • 19
    May 19th
    21 Files
  • 20
    May 20th
    15 Files
  • 21
    May 21st
    15 Files
  • 22
    May 22nd
    6 Files
  • 23
    May 23rd
    0 Files
  • 24
    May 24th
    0 Files
  • 25
    May 25th
    0 Files
  • 26
    May 26th
    0 Files
  • 27
    May 27th
    0 Files
  • 28
    May 28th
    0 Files
  • 29
    May 29th
    0 Files
  • 30
    May 30th
    0 Files
  • 31
    May 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2020 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close