The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
High
AC
The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques. The attacker must have additional methods available to bypass security measures in place. For example, circumvention of address space randomization (ASLR) or data execution prevention must be performed for the attack to be successful. Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Scope
S
An exploited vulnerability can affect resources beyond the security scope managed by the security authority that is managing the vulnerable component. This is often referred to as a 'privilege escalation,' where the attacker can use the exploited vulnerability to gain control of resources that were not intended or authorized.
Confidentiality
Low
C
There is some impact on confidentiality, but the attacker either does not gain control of any data, or the information obtained does not have a significant impact on the system or its operations.
Integrity
Low
I
Modification of data is possible, but the attacker does not have control over what can be modified, or the extent of what the attacker can affect is limited. The data modified does not have a direct, serious impact on the system.
Availability
Low
A
There is reduced performance or interruptions in resource availability. However, the attacker does not have the ability to completely prevent access to the resources or services; the impact is limited.
Trend Micro Enterprise Mobile Security Android MITM SSL Certificate VulnerabilityTrend Micro Enterprise Mobile Security Android Application - MITM SSL Certificate Vulnerability (CVE-2016-9319)
--
http://www.info-sec.ca/advisories/Trend-Micro-Enterprise-Mobile-Security.html
Overview
"Trend Micro Mobile Security is the client app for Trend Micros
enterprise mobility platform. Trend Micro Mobile Security for
enterprises lets IT administrators enroll, manage and secure employee
mobile devices. With built in Mobile device management, app
management, app reputation and device AV, Mobile Security is a
powerful tool for enterprises that want to enable their mobile
employees securely."
(https://play.google.com/store/apps/details?id=com.trendmicro.tmmssuite.mdm)
Issue
The Trend Micro Enterprise Mobile Security Android application
(version 9.7.1182 and below), does not validate the SSL certificate it
receives when connecting to the mobile application login server.
Impact
An attacker who can perform a man in the middle attack may present a
bogus SSL certificate which the application will accept silently.
Sensitive information could be captured by an attacker without the
user's knowledge.
Timeline
October 23, 2016 - Notified Trend Micro via security () trendmicro com
October 23, 2016 - Trend Micro responded that they will investigate
October 24, 2016 - Trend Micro asked for steps to reproduce the vulnerability
October 25, 2016 - Provided steps to reproduce
November 7, 2016 - Trend Micro confirmed the vulnerability
January 25, 2017 - Trend Micro stated that they expect the vulnerability to be resolved in the next version
February 15, 2017 - Trend Micro released version 9.7.1193 which resolves this vulnerability
March 29, 2017 - Trend Micro completed the localization and deployment of version 9.7.1193 to all regions
Solution
Upgrade to version 9.7.1193 or later
https://success.trendmicro.com/solution/1116973
CVE-ID:
CVE-2016-9319
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum