CVE-2016-10493

Status: Analyzed

Last modified: 01-05-2018

Published: 18-04-2018

9.8

SUMMARY CVE-2016-10493

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, and SDX20, NPA routines on the rootPD that handle resource requests remoted over QDI may not validate pointers passed from user space which may result in guest OS memory corruption.

Access CVSS3 CVE-2016-10493

Attack Complexity	Attack Vector	Privileges Required	Scope	User Interaction
LOW	NETWORK	NONE	UNCHANGED	NONE

Impact CVSS3 CVE-2016-10493

Confidentiality	Integrity	Availability
HIGH	HIGH	HIGH

Details CVE-2016-10493

EPSS	0.00187
EPSS %	0.56612
References	http://www.securityfocus.com/bid/103671 https://source.android.com/security/bulletin/2018-04-01
CWE	CWE-119
CAPEC	Buffer Overflow via Environment Variables: This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables. Overflow Buffers: Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice. Buffer Manipulation: An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory. Client-side Injection-induced Buffer Overflow: This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service. This hostile service is created to deliver the correct content to the client software. For example, if the client-side application is a browser, the service will host a webpage that the browser loads. Filter Failure through Buffer Overflow: In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered). MIME Conversion: An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back. Overflow Binary Resource File: An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the adversary access to the execution stack and execute arbitrary code in the target process. Buffer Overflow via Symbolic Links: This type of attack leverages the use of symbolic links to cause buffer overflows. An adversary can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking. Overflow Variables and Tags: This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The adversary crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow. Buffer Overflow via Parameter Expansion: In this attack, the target software is given input that the adversary knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow. Buffer Overflow in an API Call: This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An adversary who has knowledge of known vulnerable libraries or shared code can easily target software that makes use of these libraries. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process. Buffer Overflow in Local Command-Line Utilities: This attack targets command-line utilities available in a number of shells. An adversary can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Vulnerable Configurations	cpe:2.3:o:qualcomm:mdm9206_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9206_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9206:-:::::::* cpe:2.3:h:qualcomm:mdm9206:-:::::::* cpe:2.3:o:qualcomm:mdm9607_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9607_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9607:-:::::::* cpe:2.3:h:qualcomm:mdm9607:-:::::::* cpe:2.3:o:qualcomm:mdm9635m_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9635m_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9635m:-:::::::* cpe:2.3:h:qualcomm:mdm9635m:-:::::::* cpe:2.3:o:qualcomm:mdm9640_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9640_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9640:-:::::::* cpe:2.3:h:qualcomm:mdm9640:-:::::::* cpe:2.3:o:qualcomm:mdm9645_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9645_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9645:-:::::::* cpe:2.3:h:qualcomm:mdm9645:-:::::::* cpe:2.3:o:qualcomm:mdm9650_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9650_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9650:-:::::::* cpe:2.3:h:qualcomm:mdm9650:-:::::::* cpe:2.3:o:qualcomm:mdm9655_firmware:-:::::::* cpe:2.3:o:qualcomm:mdm9655_firmware:-:::::::* cpe:2.3:h:qualcomm:mdm9655:-:::::::* cpe:2.3:h:qualcomm:mdm9655:-:::::::* cpe:2.3:o:qualcomm:msm8909w_firmware:-:::::::* cpe:2.3:o:qualcomm:msm8909w_firmware:-:::::::* cpe:2.3:h:qualcomm:msm8909w:-:::::::* cpe:2.3:h:qualcomm:msm8909w:-:::::::* cpe:2.3:o:qualcomm:sd_210_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_210_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_210:-:::::::* cpe:2.3:h:qualcomm:sd_210:-:::::::* cpe:2.3:o:qualcomm:sd_212_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_212_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_212:-:::::::* cpe:2.3:h:qualcomm:sd_212:-:::::::* cpe:2.3:o:qualcomm:sd_205_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_205_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_205:-:::::::* cpe:2.3:h:qualcomm:sd_205:-:::::::* cpe:2.3:o:qualcomm:sd_425_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_425_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_425:-:::::::* cpe:2.3:h:qualcomm:sd_425:-:::::::* cpe:2.3:o:qualcomm:sd_430_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_430_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_430:-:::::::* cpe:2.3:h:qualcomm:sd_430:-:::::::* cpe:2.3:o:qualcomm:sd_450_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_450_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_450:-:::::::* cpe:2.3:h:qualcomm:sd_450:-:::::::* cpe:2.3:o:qualcomm:sd_415_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_415_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_415:-:::::::* cpe:2.3:h:qualcomm:sd_415:-:::::::* cpe:2.3:o:qualcomm:sd_617_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_617_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_617:-:::::::* cpe:2.3:h:qualcomm:sd_617:-:::::::* cpe:2.3:o:qualcomm:sd_625_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_625_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_625:-:::::::* cpe:2.3:h:qualcomm:sd_625:-:::::::* cpe:2.3:o:qualcomm:sd_650_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_650_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_650:-:::::::* cpe:2.3:h:qualcomm:sd_650:-:::::::* cpe:2.3:o:qualcomm:sd_652_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_652_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_652:-:::::::* cpe:2.3:h:qualcomm:sd_652:-:::::::* cpe:2.3:o:qualcomm:sd_808_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_808_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_808:-:::::::* cpe:2.3:h:qualcomm:sd_808:-:::::::* cpe:2.3:o:qualcomm:sd_810_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_810_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_810:-:::::::* cpe:2.3:h:qualcomm:sd_810:-:::::::* cpe:2.3:o:qualcomm:sd_820_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_820_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_820:-:::::::* cpe:2.3:h:qualcomm:sd_820:-:::::::* cpe:2.3:o:qualcomm:sd_835_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_835_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_835:-:::::::* cpe:2.3:h:qualcomm:sd_835:-:::::::* cpe:2.3:o:qualcomm:sd_845_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_845_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_845:-:::::::* cpe:2.3:h:qualcomm:sd_845:-:::::::* cpe:2.3:o:qualcomm:sdx20_firmware:-:::::::* cpe:2.3:o:qualcomm:sdx20_firmware:-:::::::* cpe:2.3:h:qualcomm:sdx20:-:::::::* cpe:2.3:h:qualcomm:sdx20:-:::::::* cpe:2.3:o:qualcomm:sd_850_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_850_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_850:-:::::::* cpe:2.3:h:qualcomm:sd_850:-:::::::* cpe:2.3:o:qualcomm:sd_820a_firmware:-:::::::* cpe:2.3:o:qualcomm:sd_820a_firmware:-:::::::* cpe:2.3:h:qualcomm:sd_820a:-:::::::* cpe:2.3:h:qualcomm:sd_820a:-:::::::*
CVSS3 Source	nvd@nist.gov
CVSS3 Type	Primary
CVSS3 Vector	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H