Wise Care 365 4.27 / Wise Disk Cleaner 9.29 Privilege Escalation
Posted on 24 September 2016
# Exploit Title: Wisecleaner Software Multiple Unquoted Service Path Elevation of Privilege # Date: 23/09/2016 # Exploit Author: Tulpa # Contact: tulpa@tulpa-security.com # Author website: www.tulpa-security.com # Vendor Homepage: http://www.wisecleaner.com # Software Link: http://www.wisecleaner.com/wise-disk-cleaner.html, http://www.wisecleaner.com/wise-care-365.html # Version: Wise Care 365 4.27, Wise Disk Cleaner 9.29 # Tested on: Windows 7 x86 # Shout-out to carbonated and ozzie_offsec 1. Description: Two seperate instances of unquoted service path privilege escalation has been discovered. The first instance is within Wise Care 365 4.27 which installs a vulnerable service entitled WiseBootAssistant. The second vulnerability exists when Wise Disk Cleaner 9.29 installs SpyHunter 4. Both of these services run 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 Wise Disk Cleaner 9.29 C:>sc qc WiseBootAssistant [SC] QueryServiceConfig SUCCESS SERVICE_NAME: WiseBootAssistant TYPE : 110 WIN32_OWN_PROCESS (interactive) START_TYPE : 2 AUTO_START ERROR_CONTROL : 1 NORMAL BINARY_PATH_NAME : C:Program FilesWiseWise Care 365BootTime.exe LOAD_ORDER_GROUP : TAG : 0 DISPLAY_NAME : Wise Boot Assistant DEPENDENCIES : SERVICE_START_NAME : LocalSystem SpyHunter 4 C:>sc qc "SpyHunter 4 Service" [SC] QueryServiceConfig SUCCESS SERVICE_NAME: SpyHunter 4 Service TYPE : 10 WIN32_OWN_PROCESS START_TYPE : 2 AUTO_START ERROR_CONTROL : 1 NORMAL BINARY_PATH_NAME : C:Program FilesEnigma Software GroupSpyHunterSH4Service.exe LOAD_ORDER_GROUP : Base TAG : 0 DISPLAY_NAME : SpyHunter 4 Service DEPENDENCIES : SERVICE_START_NAME : LocalSystem 3. Exploit: A successful attempt would require the local user to be able to insert their code in the system root path undetected by the OS or other security applications where it could potentially be executed during application startup or reboot. If successful, the local user's code would execute with the elevated privileges of the application.
