ID CVE-2015-9166
Summary In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, and SD 850, DRM provisioning mechanisms used in QSEE applications have a feature to prevent further provisioning. This is done by creating an SFS file called 'finalize_prov_flag.data' at the end of provisioning. When this feature is enabled, provisioning calls check for the existence of the file in order to decide whether to do provisioning or not. Current implementation allows provisioning without sufficient checks.
References
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:ipq4019_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:qualcomm:ipq4019_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:qualcomm:ipq4019:-:*:*:*:*:*:*:*
    cpe:2.3:h:qualcomm:ipq4019:-:*:*:*:*:*:*:*
  • 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:-:*:*:*:*:*:*:*
  • 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: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_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_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_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_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: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:-:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 11-05-2018 - 14:04)
Impact:
Exploitability:
CWE CWE-19
CAPEC
  • XML Oversized Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
  • 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.
  • XML Nested Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:P/A:N
refmap via4
bid 103671
confirm https://source.android.com/security/bulletin/2018-04-01
Last major update 11-05-2018 - 14:04
Published 18-04-2018 - 14:29
Last modified 11-05-2018 - 14:04
Back to Top