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.


Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

December 2019

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close