Vulnerability
CVE-2020-3639
Component: CELLULAR
Location: FIRMWARE
u'When a non standard SIP sigcomp message is received from the network, then there may be chances of using more UDVM cycle or memory overflow' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8009, APQ8017, APQ8037, APQ8053, MDM9250, MDM9607, MDM9628, MDM9640, MDM9650, MSM8108, MSM8208, MSM8209, MSM8608, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, QCM4290, QCM6125, QCS410, QCS4290, QCS603, QCS605, QCS610, QCS6125, QM215, QSM8350, SA415M, SA6145P, SA6150P, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA429W, SDA640, SDA660, SDA670, SDA845, SDA855, SDM1000, SDM429, SDM429W, SDM439, SDM450, SDM455, SDM630, SDM632, SDM636, SDM640, SDM660, SDM670, SDM710, SDM712, SDM845, SDM850, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM7125, SM7150, SM7150P, SM7250, SM7250P, SM8150, SM8150P, SM8350, SM8350P, SXR1120, SXR1130
Impact
Severity (Manufact.)
CRITICAL
Severity (NIST)
9.8
Severity (Android)
N/A
Chipsets
32
Devices
1407
Affected Hardware
| Name | Also known as | Manufacturer |
|---|---|---|
| MSM8905 | Qualcomm 205 | Qualcomm |
| MSM8208 | Snapdragon 208 | Qualcomm |
| MSM8909 | Snapdragon 210 | Qualcomm |
| QM215 | Qualcomm 215 | Qualcomm |
| MSM8917 | Snapdragon 425 | Qualcomm |
| MSM8920 | Snapdragon 427 | Qualcomm |
| MSM8937 | Snapdragon 430 | Qualcomm |
| MSM8940 | Snapdragon 435 | Qualcomm |
| SDM429 | Snapdragon 429 | Qualcomm |
| SDM439 | Snapdragon 439 | Qualcomm |
32 of 32 row(s) shown.
Rows per page
Page 1 of 4
Information reliability
The information on this website is intended to provide information on the big picture of chipset security and measure trends within the industry. Our information is obtained from several vantage points, checked for consistency, and automatically cross-referenced. However, this process may not always yield reliable information. Do not use the information on a particular vulnerability, chipset or device to verify your individual exposure in cases where inaccuracies are inacceptable, for instance to assess risks if you are a Politically Exposed Person.
Timeline
Introduced (est):
Jan 1, 2014
Reported:
Unknown
Advisory Published:
Nov 2, 2020
CVE Published:
Nov 12, 2020
Android Patch Level:
Nov 2020
