|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you have found a vulnerability, please send to our SecurityAlert Database : secalert()securityreason()com
Also if you have new ( 0-day ) exploit, please send to our ExploitAlert Archive :
exploit()securityreason()com |
|
|
Home SecurityAlert Database |
|
|
Topic : | HTC / Windows Mobile OBEX FTP Service Directory Traversal Vulnerability
|
SecurityAlert : 4938
CVE : CVE-2009-0244
CWE : CWE-22
SecurityRisk : High (About)
Remote Exploit : Yes
Local Exploit : No
Victim interaction required : Yes
Exploit Available : Yes
Credit : Alberto Moreno Tablado
Published : 23.01.2009
Updated : 08.07.2009
Author Note : | There exists a Directory Traversal vulnerability in the OBEX FTP Service in the Bluetooth Stack implemented in HTC devices running Windows Mobile 6 and Windows Mobile 6.1. The OBEX FTP server is located in \Windows\obexfile.dll.
Microsoft states this is a 3rd party driver developed by HTC and installed on HTC devices running Windows Mobile, so the vulnerability only affects to this vendor specifically. The vendor, HTC, has been contacted since February 2009 but presently no patches are known to be released for this security flaw.
This vulnerability is a zero-day threat. This means that all HTC devices running Windows Mobile 6 and Windows Mobile 6.1 shipped up to date (July 2009) may be vulnerable. |
Affected Software : | microsoft:windows_mobile:6.0
microsoft:windows_mobile:6.1 |
 Advisory Content : Title: Microsoft Bluetooth Stack OBEX Directory Traversal
Author: Alberto Moreno Tablado
Vendor: Microsoft
Product: Windows Mobile 6 Professional (Probably Windows Mobile 5.0 for
Pocket PC and Windows Mobile 5.0 for Pocket PC Phone Edition)
References:
http://www.seguridadmobile.com/windows-mobile/windows-mobile-security/Mi
crosoft-Bluetooth-Stack-Directory-Traversal.html
Description:
Most Windows Mobile 5.0 & 6 devices are shipped with Microsoft Bluetooth
stack, only few of them use others like Widcomm Bluetooth stack. Among all
the Bluetooth services that may be implemented in the stack, OBEX FTP is
the most common service.
OBEX FTP Bluetooth service can be used to share files through Bluetooth,
not only by sending files but also by allowing remote devices to browse
local shared folders and download files. Usually, the service is configured
in such a way that a specific directory is shared and the user can place
there all the files he would like to share with other people. The default
directory is My Device\My Documents\Bluetooth Share. A different directory
may be selected by the user, however the Bluetooth wizard usually doesn't
allow specifying any other from the filesystem out of My Device\My
Documents\ or Memory Card\My Documents\ paths. This is because of safety
reasons, so the user can't expose sensitive files or information through
Bluetooth.
There exists a Directory Traversal vulnerability in the OBEX FTP Service in
Microsoft Bluetooth Stack implemented in Windows Mobile 5.0 & 6 devices. A
remote attacker (who previously owned authentication and authorization
rights) can use tools like ObexFTP to traverse to parent directories out of
the default Bluetooth shared folder. This means the attacker can browse
folders located on a lower level, download files contained in those folders
as well as upload files to those folders.
The only requirement is that the attacker must have authentication and
authorization privileges over the OBEX FTP service. Pairing up with the
remote Windows Mobile device should be enough to get it. In case the
attacker succeeded in getting the proper privileges, further actions will
be transparent to the user.
As described above, the attacker can take three risky actions:
- Browse directories located out of the limits of the default shared folder
and discover sensitive information about the structure of the filesystem.
- Download sensitive files located anywhere in the filesystem, such as
personal pictures and documents, emails located in \Windows\Messaging or
Contacts+Calendar+Tasks information included in \PIM.vol.
- Upload dangerous files like trojans to any place in the filesystem, such
as \Windows\Startup.
In the following capture, the attacker firstly lists the default Bluetooth
shared folder. After that, the attacker puts a trojan.exe file in the
\Windows\Startup folder.
gospel@gospel-shift:~/bluez$ obexftp -b 00:17:83:02:BA:3C -l
Browsing 00:17:83:02:BA:3C ...
Channel: 4
Connecting...done
Receiving "(null)"... <?xml version="1.0"?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<folder-listing version="1.0">
<parent-folder name="" />
<file name="fotaca.jpg" created="20090119T173932Z" size="134680"/>
<file name="nota.pwi" created="20090119T175242Z" size="432"/>
</folder-listing>
done
Disconnecting...done
gospel@gospel-shift:~/bluez$ obexftp -b 00:17:83:02:BA:3C -c
"..\\..\\Windows\\Startup\\" -p trojan.exe
Browsing 00:17:83:02:BA:3C ...
Channel: 4
Connecting...done
Sending "..\..\Windows\Inicio\"... done
Sending "trojan.exe"...\done
Disconnecting...done
gospel@gospel-shift:~/bluez$
The trojan file will be executed the next time Windows Mobile inits.
Workaround:
Do not accept pairing nor connection requests from unknown sources. Delete
old entries in the paired devices list. Wait for proper vendor response and
updates.
References :
http://www.seguridadmobile.com/windows-mobile/windows-mobile-security/HTC-Windows-Mobile-OBEX-FTP-Service-Directory-Traversal.html
http://www.securityfocus.com/bid/33359
http://www.securityfocus.com/archive/1/archive/1/500199/100/0/threaded
Feedback :
If you have additional information or notice any errors regarding this security advisory, please use contact form or email us at info()securityreason()com.
|
|
|
|