ID CVE-2015-9142
Summary In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9645, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, bounds check is missing for vtable index in DAL-TO-QDI conversion framework.
References
Vulnerable Configurations
  • 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: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_400_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_400_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_400:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_400:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sd_410_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_410_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_410:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_410:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sd_412_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_412_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_412:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_412:-:*:*:*:*:*:*:*
  • 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_615_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_615_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_615:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_615:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sd_616_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_616_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_616:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_616:-:*:*:*:*:*:*:*
  • 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_427_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_427_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_427:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_427:-:*:*:*:*:*:*:*
  • 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_800_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_800_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_800:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_800:-:*:*:*:*:*:*:*
  • 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_435_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sd_435_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sd_435:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sd_435:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sdm630_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sdm630_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sdm630:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sdm630:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sdm636_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sdm636_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sdm636:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sdm636:-:*:*:*:*:*:*:*
  • cpe:2.3:o:qualcomm:sdm660_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:sdm660_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:sdm660:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:sdm660:-:*:*:*:*:*:*:*
CVSS
Base: 10.0 (as of 09-05-2018 - 16:52)
Impact:
Exploitability:
CWE CWE-118
CAPEC
  • 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 attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. 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 via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker 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.
  • 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).
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker 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 Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
  • 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.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker 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.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
cvss-vector via4 AV:N/AC:L/Au:N/C:C/I:C/A:C
refmap via4
bid 103671
confirm https://source.android.com/security/bulletin/2018-04-01
Last major update 09-05-2018 - 16:52
Published 18-04-2018 - 14:29
Last modified 09-05-2018 - 16:52
Back to Top