Qualcomm Snapdragon Auto up to SDX20 Header memory corruption

Summaryinfo

A vulnerability classified as critical has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IoT, Snapdragon IoT, Snapdragon Mobile and Snapdragon Wearables. This affects an unknown function of the component Header Handler. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2019-2248. The attack is only possible with local access. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IoT, Snapdragon IoT, Snapdragon Mobile and Snapdragon Wearables (Chip Software). This affects some unknown processing of the component Header Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow can occur if invalid header tries to overwrite the existing buffer which fix size allocation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 820, SD 820A, SD 845 / SD 850, SDM439, SDM660, SDX20

The weakness was released 05/24/2019 (Website). The advisory is shared at codeaurora.org. This vulnerability is uniquely identified as CVE-2019-2248 since 12/10/2018. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/16/2020).

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 VDB-135515, VDB-135516, VDB-135517 and VDB-135518. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Chip Software

Vendor

• Qualcomm

Name

• Snapdragon Auto
• Snapdragon Compute
• Snapdragon Connectivity
• Snapdragon Consumer IoT
• Snapdragon IoT
• Snapdragon Mobile
• Snapdragon Wearables

Version

• 16
• 52
• MSM8909W
• MSM8996AU
• Qualcomm 215
• SD 415
• SD 429
• SD 439
• SD 450
• SD 615
• SD 625
• SD 632
• SD 636
• SD 650
• SD 820
• SD 820A
• SD 845
• SD 850
• SDM439
• SDM660
• SDX20

License

• commercial

Website

• Vendor: https://www.qualcomm.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion