Qualcomm Snapdragon Mobile up to SD 850 font_mgr_qsee_request_service memory corruption

A vulnerability was found in Qualcomm Snapdragon Mobile, Snapdragon Wear and Snapdragon Automobile (Chip Software) and classified as critical. This issue affects the function font_mgr_qsee_request_service. The manipulation with an unknown input leads to a memory corruption vulnerability (Integer Underflow). Using CWE to declare the problem leads to CWE-191. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An integer underflow may occur due to lack of check when received data length from font_mgr_qsee_request_service is bigger than the minimal value of the segment header, which may result in a buffer overflow, in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850.

The weakness was released 05/06/2019. The identification of this vulnerability is CVE-2017-18278 since 05/18/2018. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/07/2019).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Entries connected to this vulnerability are available at 134408 and 134409.

Vendor

Name

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: ≈5.5
VulDB Temp Score: ≈5.5
VulDB Vector: ?
VulDB Reliability: ?

VulDB Base Score: ?
VulDB Temp Score: ?
VulDB Reliability: ?
Class: Memory corruption / Integer Underflow (CWE-191)
Local: Yes
Remote: No

Availability: ?
Status: Not defined

Price Prediction: ?
Current Price Estimation: ?

Threat Intelligenceinfoedit

Threat: ?
Adversaries: ?
Geopolitics: ?
Economy: ?
Predictions: ?
Remediation: ?Recommended: no mitigation known
0-Day Time: ?05/18/2018 CVE assigned
05/06/2019 +353 days Advisory disclosed
05/07/2019 +1 days VulDB entry created
05/07/2019 +0 days VulDB last updateCVE: CVE-2017-18278 (?)
See also: ?Created: 05/07/2019 07:11 AM
Complete: ?

Comments are closed.