bugtraq - DDIVRT-2008-11 BadBlue uninst.exe DoS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20080424120841.16241.qmail@securityfocus.com>
Date: 24 Apr 2008 12:08:41 -0000
From: vulnerabilityresearch@...italdefense.net
To: bugtraq@...urityfocus.com
Subject: DDIVRT-2008-11 BadBlue uninst.exe DoS

Title
-----
DDIVRT-2008-11 BadBlue uninst.exe DoS

Severity
--------
Medium

Date Discovered
---------------
March 5th 2008

Discovered By
-------------
Digital Defense, Inc. Vulnerability Research Team
Credit: Steven James and r@...$

Vulnerability Description
-------------------------
BadBlue is a web server used for peer-to-peer file sharing. By default, several executable files are stored in the web root: badblue.exe, uninst.exe, and dyndns.exe. Executable files stored in the web root of BadBlue can be launched remotely by any user. This can be leveraged to create a DoS condition by repeatedly invoking the uninst.exe executable. Due to the fact that BadBlue has not released a patch for the previously documented directory traversal vulnerability (CVE 2007-6378), an attacker may utilize these two flaws in conjunction to place a malicious executable in the web root and compromise a vulnerable server. 

Solution Description
--------------------
Restrict access to the executables already in the web root (badblue.exe, uninst.exe, and dyndns.exe) and take steps to ensure that users cannot write files to the web root.

Tested Systems / Software (with versions)
------------------------------------------
BadBlue Personal Edition version 2.72 has been tested on Windows XP and Windows Server 2003.  Other versions and systems are assumed to be vulnerable.

Vendor Contact
--------------
Vendor Name: BadBlue
Vendor Website: www.badblue.com