Chipset
Qualcomm SDM660
Also known as Snapdragon 660
Statistics
Released (est):
April 2017
8 years ago
Vulnerabilities:
474
Devices:
68
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2018-5383 | HIGH | BLUETOOTH | FIRMWARE | Jan 18, 2018 | Apr 2024 | Aug 2018 |
| CVE-2023-33018 | HIGH | DEBUG | N/A | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33054 | CRITICAL | POSITION | OS | Mar 18, 2023 | Dec 2023 | Dec 2023 |
| CVE-2023-33063 | HIGH | N/A | OS | Dec 18, 2022 | Dec 2023 | Dec 2023 |
| CVE-2023-33070 | HIGH | N/A | OS | Nov 17, 2022 | Dec 2023 | N/A |
| CVE-2023-33080 | HIGH | WIFI | FIRMWARE | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33031 | HIGH | AUDIO | OS | Mar 21, 2023 | Nov 2023 | Nov 2023 |
| CVE-2023-33059 | HIGH | AUDIO | OS | Mar 24, 2023 | Nov 2023 | Nov 2023 |
| CVE-2022-33275 | HIGH | WIFI | N/A | Jun 10, 2022 | Sep 2023 | Jan 2024 |
| CVE-2022-22076 | HIGH | TRUST | N/A | May 5, 2022 | Jun 2023 | Dec 2023 |
474 of 474 row(s) shown.
Rows per page
Page 1 of 48
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Asus Zenfone Max Pro (M2) ZB631KL | X01BDA | ASUS | Dec 1, 2018 |
| Asus Zenfone Max Pro (M2) ZB631KL | Zenfone Max Pro M2 | ASUS | Dec 1, 2018 |
| Asus Zenfone Max Pro (M2) ZB631KL | ZB631KL | ASUS | Dec 1, 2018 |
| Cat S62 | Cat S62 | CAT | Jun 18, 2021 |
| Cat S62 Pro | Cat S62 Pro | CAT | Aug 17, 2020 |
| Gionee M7 Plus | Gionee M7 Plus | GIONEE | Jul 1, 2018 |
| Meizu 15 | Meizu 15 | MEIZU | Apr 1, 2018 |
| Sharp Aquos S3 High | Sharp Aquos S3 High | SHARP | Jul 1, 2018 |
| Nokia 7.2 | TA-1193 | NOKIA | Sep 23, 2019 |
| Nokia 7.2 | TA-1178 | NOKIA | Sep 23, 2019 |
68 of 68 row(s) shown.
Rows per page
Page 1 of 7
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.
