Chipset
Qualcomm MSM8230
Also known as Snapdragon 400
Statistics
Released (est):
January 2013
12 years ago
Vulnerabilities:
12
Devices:
45
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2023-33066 | HIGH | AUDIO | OS | Mar 21, 2023 | Mar 2024 | Mar 2024 |
| CVE-2020-11170 | CRITICAL | AUDIO | N/A | N/A | Feb 2021 | Feb 2021 |
| CVE-2020-11136 | CRITICAL | AUDIO | OS | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11137 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11138 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11143 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3685 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3686 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3691 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2017-18172 | N/A | TRUST | N/A | N/A | Oct 2018 | Jul 2018 |
12 of 12 row(s) shown.
Rows per page
Page 1 of 2
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Gionee Ctrl V6L | Gionee Ctrl V6L | GIONEE | Nov 1, 2014 |
| HTC Desire 825 | Desire 825 | HTC | Apr 1, 2016 |
| HTC Desire 825 | Desire 825 dual sim | HTC | Apr 1, 2016 |
| HTC Desire 630 | Desire 630 dual sim | HTC | Jun 1, 2016 |
| HTC Desire 612 | HTC Desire 612 | HTC | Oct 1, 2014 |
| HTC Desire 816 dual sim | Desire 816 dual sim | HTC | May 1, 2014 |
| HTC Desire 816 dual sim | Desire_816_dual_sim | HTC | May 1, 2014 |
| HTC One mini 2 | One mini 2 | HTC | May 1, 2014 |
| HTC One Remix | HTC6515LVW | HTC | Jul 1, 2014 |
| HTC Desire 610 | Desire 610 | HTC | May 1, 2014 |
45 of 45 row(s) shown.
Rows per page
Page 1 of 5
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.
