Qualcomm Snapdragon Mobile Vulnerabilities

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

QCS605349
MSM8996AU335
SDA660326
SDM660321
SDM630294

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

Official Fix945
Temporary Fix0
Workaround0
Unavailable0
Not Defined126

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

High0
Functional0
Proof-of-Concept1
Unproven0
Not Defined1070

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

Not Defined0
Physical10
Local551
Adjacent150
Network360

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

Authentication

Not Defined0
High26
Low610
None435

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

User Interaction

Not Defined0
Required29
None1042

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

≤10
≤21
≤30
≤48
≤563
≤6116
≤7432
≤8216
≤9205
≤1030

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

≤10
≤21
≤30
≤49
≤567
≤6139
≤7424
≤8245
≤9159
≤1027

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

≤10
≤21
≤35
≤483
≤535
≤6485
≤764
≤8336
≤932
≤1030

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

≤10
≤20
≤30
≤40
≤52
≤684
≤737
≤8440
≤922
≤10219

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

CNA

≤10
≤20
≤30
≤40
≤51
≤68
≤735
≤884
≤960
≤1015

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

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

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

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

Exploit 0-day

<1k2
<2k13
<5k84
<10k417
<25k512
<50k43
<100k0
≥100k0

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

<1k549
<2k156
<5k261
<10k85
<25k20
<50k0
<100k0
≥100k0

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 (231): 12, 16, 52, 212-SD 205, APQ8009, APQ8009W, APQ8016, APQ8017, APQ8037, APQ8052, APQ8053, APQ8056, APQ8064, APQ8064AU, APQ8076, APQ8096, APQ8096AU, APQ8096SG, APQ8098, AR9344, Agatti, Bitra, FSM9055, FSM9955, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM8207, MDM9150, MDM9205, MDM9206, MDM9207, MDM9207C, MDM9250, MDM9607, MDM9615, MDM9625, MDM9628, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MMDM9206, 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, QCA9378, QCA9379, QCA9531, QCA9558, QCA9563, QCA9880, 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 210-SD 212-SD 205, SD 212, SD 215, SD 400, SD 410, SD 410-12, SD 415, SD 425, SD 427, SD 429, SD 429, SD 430, SD 435, SD 439, SD 439 - SD 429, SD 450, SD 600, SD 602A, SD 615, SD 615-16, SD 615-16-SD 415, SD 617, SD 625, SD 632, SD 636, SD 650, SD 650-52, SD 665, SD 670, SD 675, SD 710, SD 712, SD 712 - SD 710 - SD 670, SD 730, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 820Am, 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, SDX206, 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/15/20227.57.3Qualcomm Snapdragon Mobile Modem denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix1.51CVE-2022-25671
11/15/20227.06.8Qualcomm Snapdragon Auto WLAN infinite loop$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-33239
11/15/20227.06.8Qualcomm Snapdragon Auto WLAN buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.09CVE-2022-33237
11/15/20227.06.8Qualcomm Snapdragon Compute WLAN buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-33236
11/15/20227.37.1Qualcomm Snapdragon Auto Video memory corruption$5k-$25k$5k-$25kNot DefinedOfficial Fix0.00CVE-2022-33234
11/15/20228.68.4Qualcomm Snapdragon Auto Graphics Import use after free$25k-$100k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-25743
11/15/20227.06.8Qualcomm Snapdragon Auto WLAN null pointer dereference$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-25741
11/15/20228.88.4Qualcomm Snapdragon Auto Graphics buffer overflow$25k-$100k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-25724
11/15/20226.46.2Qualcomm Snapdragon Compute Broadcast Receiver denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-25679
11/15/20224.34.1Qualcomm Snapdragon Auto GATT null pointer dereference$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-25710
11/15/20226.56.4Qualcomm Snapdragon Auto AVI File Parser buffer overflow$5k-$25k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-25676
10/19/20227.77.6Qualcomm Snapdragon Auto Metadata memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-33214
10/19/20228.38.2Qualcomm Snapdragon Mobile BTHOST memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.44CVE-2022-25750
10/19/20227.57.3Qualcomm Snapdragon Auto WLAN denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-25749
10/19/20229.89.6Qualcomm Snapdragon Auto WLAN integer overflow$25k-$100k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25748
10/19/20227.57.3Qualcomm Snapdragon Auto WLAN denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-25736
10/19/20228.07.9Qualcomm Snapdragon Mobile Multimedia use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.18CVE-2022-25723
10/19/20229.89.6Qualcomm Snapdragon Auto WLAN memory corruption$25k-$100k$5k-$25kNot DefinedOfficial Fix0.04CVE-2022-25720
10/19/20228.48.3Qualcomm Snapdragon Auto WLAN improper authentication$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-25718
10/19/20227.87.7Qualcomm Snapdragon Auto ASF Clip Parser memory corruption$5k-$25k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-25687
10/19/20226.76.5Qualcomm Snapdragon Auto use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25666
10/19/20224.64.5Qualcomm Snapdragon Auto Boot denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2022-22078
10/19/20227.87.5Qualcomm Snapdragon Mobile Graphics use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-22077
10/19/20227.87.6Qualcomm Snapdragon Mobile IPC memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.33CVE-2022-33217
10/19/20227.57.5Qualcomm Snapdragon Auto WLAN information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.42CVE-2022-25719
10/19/20225.05.0Qualcomm Snapdragon Auto GPU information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.15CVE-2022-25664
10/19/20227.27.2Qualcomm Snapdragon Auto Kernel null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25661
10/19/20226.56.4Qualcomm Snapdragon Auto Kernel memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-25660
10/19/20225.75.7Qualcomm Snapdragon Auto Kernel information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25665
10/19/20226.06.0Qualcomm Snapdragon Auto Kernel information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25662
09/27/20228.07.9Qualcomm Snapdragon Auto ION use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-22058
09/16/20229.89.6Qualcomm Snapdragon Connectivity/Snapdragon Mobile WLAN Key Parser memory corruption$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-25708
09/16/20227.67.5Qualcomm Snapdragon Auto memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25696
09/16/20228.38.2Qualcomm Snapdragon Connectivity/Snapdragon Mobile Graphics use after free$25k-$100k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-25693
09/16/20227.87.7Qualcomm Snapdragon Auto ps Clip memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25688
09/16/20227.87.7Qualcomm Snapdragon Auto WAV File memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25686
09/16/20227.57.3Qualcomm Snapdragon Auto WLAN denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-25670
09/16/20225.95.8Qualcomm Snapdragon Auto MP4 Clip Parser buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25669
09/16/20228.68.4Qualcomm Snapdragon Auto Console memory corruption$25k-$100k$5k-$25kNot DefinedOfficial Fix0.02CVE-2022-25656
09/16/20228.88.7Qualcomm Snapdragon Auto HFP-UNIT Profile memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-22105
09/16/20228.38.2Qualcomm Snapdragon Compute synx Driver use after free$25k-$100k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-22095
09/16/20227.57.3Qualcomm Snapdragon Auto LTE Security Mode Command denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-22091
09/16/20228.38.2Qualcomm Snapdragon Connectivity Audio memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-22089
09/16/20228.38.2Qualcomm Snapdragon Auto Audio Module memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-22081
09/16/20228.38.2Qualcomm Snapdragon Auto wma File Playback memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.10CVE-2022-22074
09/16/20228.38.2Qualcomm Snapdragon Auto HLOS memory corruption$25k-$100k$5k-$25kNot DefinedOfficial Fix0.00CVE-2022-22066
09/16/20227.06.9Qualcomm Snapdragon Auto Bluetooth Driver information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25706
09/16/20226.46.3Qualcomm Snapdragon Auto ANQP Action Frame information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25690
09/16/20226.26.1Qualcomm Snapdragon Compute information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-25653
09/16/20227.97.7Qualcomm Snapdragon Compute Kernel memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-22094

1021 more entries are not shown

more entries by Qualcomm

Interested in the pricing of exploits?

See the underground prices here!