Droid4X Privilege Escalation Vulnerability

2016-11-10T00:00:00
ID 1337DAY-ID-26298
Type zdt
Reporter Yunus YILDIRIM
Modified 2016-11-10T00:00:00

Description

Droid4XService (Droid4XService.exe) installs as a service with an unquoted service path running with SYSTEM privileges. This could potentially allow an authorized but non-privileged local user to execute arbitrary code with elevated privileges on the system.

                                        
                                            # Exploit Title: Droid4X Unquoted Service Path Privilege Escalation
# Date: 03/10/2016
# Author: Yunus YILDIRIM (Th3GundY)
# Team: CT-Zer0 (@CRYPTTECH) && Superbug (@xsuperbug)
# Website: http://yildirimyunus.com
# Contact: [email protected]
# Category: local
# Vendor Homepage: http://www.droid4x.com/
# Software Link: http://dl.haima.me/download/DXDown/win/Z001/Droid4XInstaller.exe
# Tested on: Windows 7 x86/x64

1. Description

Droid4XService (Droid4XService.exe) installs as a service with 
an unquoted service path running with SYSTEM privileges.
This could potentially allow an authorized but non-privileged local
user to execute arbitrary code with elevated privileges on the system.


2. Proof of Concept

C:\Windows\system32>sc qc Droid4XService
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: Droid4XService
        TYPE               : 110  WIN32_OWN_PROCESS (interactive)
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : C:\Program Files (x86)\Droid4X\Droid4XService.exe
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Droid4XService
        DEPENDENCIES       :
        SERVICE_START_NAME : LocalSystem


3. Exploit:
 
A successful attempt would require the local attacker must insert an executable file
in the path of the service.
Upon service restart or system reboot, the malicious code will be run with elevated privileges.


Vulnerability Disclosure Timeline:
==================================
03/10/2016   -   Contact With Vendor
27/10/2016   -   No Response From Vendor
09/11/2016   -   Public Disclosure

#  0day.today [2018-03-12]  #