Product Qualcomm Snapdragon Compute

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version »

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation »

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability »

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector »

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication »

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction »

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index »

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year »

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base »

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp »

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB »

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD »

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

Vendor »

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research »

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day »

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today »

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume »

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year »

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities »

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (212): 12, 16, 52, 212-SD 205, APQ8009, APQ8009W, APQ8016, APQ8017, APQ8037, APQ8052, APQ8053, APQ8056, APQ8064, APQ8064AU, APQ8076, APQ8096, APQ8096AU, APQ8096SG, APQ8098, AR9344, Agatti, Bitra, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM8207, MDM9150, MDM9205, MDM9206, MDM9207, MDM9207C, MDM9250, MDM9607, MDM9615, MDM9625, MDM9628, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8108, MSM8208, MSM8209, MSM8608, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8952, MSM8953, MSM8956, MSM8976, MSM8976SG, MSM8996, MSM8996AU, MSM8996SG, MSM8998, Nicobar, QCA4010, QCA4531, QCA6174A, QCA6390, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9531, QCA9558, QCA9886, QCA9980, QCM2150, QCM4290, QCM6125, QCN5502, QCN7605, QCN7606, QCS404, QCS405, QCS410, QCS603, QCS605, QCS610, QCS4290, QCS6125, QM215, QRB5165, QSM8250, QSM8350, Qualcomm 215, Qualcomm 215SD 429, Rennell, SA415M, SA515M, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SD 8CX, SD 205, SD 210, SD 210-SD, SD 212, SD 410, SD 410-12, SD 415, SD 425, SD 427, SD 429, SD 430, SD 435, SD 439, SD 450, SD 600, SD 615, SD 615-16, SD 625, SD 632, SD 636, SD 650, SD 650-52, SD 665, SD 670, SD 675, SD 710, SD 712, SD 730, SD 800, SD 820, SD 820A, SD 835, SD 845, SD 850, SD 855, SDA429W, SDA640, SDA660, SDA670, SDA845, SDA855, SDM429, SDM429W, SDM439, SDM450, SDM455, SDM630, SDM632, SDM636, SDM640, SDM660, SDM670, SDM710, SDM712, SDM830, SDM845, SDM850, SDM1000, SDW2500, SDX20, SDX20M, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR1120, SXR1130, SXR2130, SXR2130P, Saipan, Snapdragon_High_Med_2016, WCD9330

Link to Product Website: https://www.qualcomm.com/

Software Type: Chip Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/12/20205.55.5Qualcomm Snapdragon Auto SIP sigcomp Message memory corruption$5k-$25k$5k-$25kNot DefinedOfficial Fix2.17-CVE-2020-3639
11/12/20205.55.3Qualcomm Snapdragon Compute/Snapdragon Mobile memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix2.17-CVE-2020-3632
11/12/20205.55.3Qualcomm Snapdragon Auto LibFastCV buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix1.97-CVE-2020-11207
11/12/20205.55.3Qualcomm Snapdragon Auto Fastrpc buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.07-CVE-2020-11206
11/12/20205.55.3Qualcomm Snapdragon Auto integer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix1.92-CVE-2020-11205
11/12/20205.55.3Qualcomm Snapdragon Auto Library buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix1.87-CVE-2020-11202
11/12/20205.55.3Qualcomm Snapdragon Auto Library memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix1.92-CVE-2020-11201
11/12/20205.55.3Qualcomm Snapdragon Auto ASF Clip integer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix1.97-CVE-2020-11196
11/12/20205.55.3Qualcomm Snapdragon Auto MKV Clip buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.02-CVE-2020-11193
11/12/20205.55.3Qualcomm Snapdragon Auto MP4 Clip buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix1.97-CVE-2020-11184
11/12/20205.55.3Qualcomm Snapdragon Auto Bluetooth Transport Driver use after free$5k-$25k$0-$5kNot DefinedOfficial Fix2.07-CVE-2020-11175
11/12/20205.55.3Qualcomm Snapdragon Auto Data Buffer buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.44-CVE-2020-11168
11/12/20205.55.3Qualcomm Snapdragon Auto GUID Attribute buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.42-CVE-2020-11132
11/12/20205.55.3Qualcomm Snapdragon Auto WiFi HAL buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.42-CVE-2020-11130
11/12/20205.55.3Qualcomm Snapdragon Auto Extensible Boot Loader integer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.52-CVE-2020-11127
11/12/20204.34.1Qualcomm Snapdragon Auto Gatekeeper Trustzone information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix2.14-CVE-2020-11123
11/12/20205.55.3Qualcomm Snapdragon Auto WiFi HAL buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix2.55-CVE-2020-11121
11/02/20203.53.4Qualcomm Snapdragon Auto PDU state issue$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3704
11/02/20205.55.3Qualcomm Snapdragon Auto Bluetooth buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3703
11/02/20205.55.3Qualcomm Snapdragon Auto qseecom buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3694
11/02/20205.55.3Qualcomm Snapdragon Auto qseecom buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3693
11/02/20205.55.3Qualcomm Snapdragon Auto IMEI buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2020-3692
11/02/20205.55.3Qualcomm Snapdragon Auto SMUU Configuration unknown vulnerability$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3690
11/02/20205.55.3Qualcomm Snapdragon Auto QSEE permission$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3684
11/02/20205.55.3Qualcomm Snapdragon Auto SIP Message buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-3673

more entries by Qualcomm

Do you want to use VulDB in your project?

Use the official API to access entries easily!