VYPR
Unrated severityNVD Advisory· Published Apr 18, 2018· Updated Sep 16, 2024

CVE-2014-9986

CVE-2014-9986

Description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear 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 800, SD 808, SD 810, SD 820, and SD 820A, in playready_licacq_process_response(), 'cbResponse' value is controlled by HLOS, and there is no validation on this length. If 'cbResponse' is too large, memory overread occurs.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Memory overread in Qualcomm's PlayReady license acquisition response parsing on Android devices could lead to information disclosure.

Vulnerability

In Android before the 2018-04-05 security patch level on Qualcomm Snapdragon Automobile, Mobile, and Wear platforms (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 800, SD 808, SD 810, SD 820, SD 820A), the function playready_licacq_process_response() in the PlayReady DRM implementation does not validate the cbResponse length, which is controlled by the HLOS (Host OS). If cbResponse is set to a large value, a memory overread occurs [1].

Exploitation

An attacker can exploit this vulnerability by providing a crafted PlayReady license acquisition response with an excessively large cbResponse field. The attacker must be able to send such a response to the device, for example, via a malicious application or a compromised server that the device contacts during license acquisition. No special privileges or user interaction beyond normal DRM operations are required [1].

Impact

A successful exploit results in a memory overread, which can leak sensitive information from beyond the intended buffer. This could lead to the disclosure of cryptographic keys, user data, or other secrets stored in device memory. The impact is limited to information disclosure; remote code execution is not achieved [1].

Mitigation

The vulnerability is fixed in the Android security patch level of April 5, 2018 or later. Users should ensure their devices receive and install this update. Devices that have reached end-of-life and no longer receive security patches remain vulnerable [1].

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

4
  • Range: before 2018-04-05 or earlier security patch level
  • Range: before 2018-04-05 or earlier security patch level
  • Range: before 2018-04-05 or earlier security patch level
  • Qualcomm, Inc./Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wearv5
    Range: 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 800, SD 808, SD 810, SD 820, SD 820A

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

0

No linked articles in our index yet.