215 vulnerabilitiesRanked by how likely they are to be used.
215 is made by Qualcomm. We track 15 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Qualcomm lists newer releases under their own names, such as 215 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is 215 listed under other names? Yes.
Qualcomm also lists 215 under more specific names, such as 215 Firmware and 215 Mobile. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which 215 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of 215's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which 215 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.4%CVE-2023-21631High
Weak Configuration due to improper input validation in Modem while processing LTE security mode command message received from network.
- 0.4%CVE-2023-33020High
Transient DOS in WLAN Host when an invalid channel (like channel out of range) is received in STA during CSA IE.
- 0.4%CVE-2023-33019High
Transient DOS in WLAN Host while doing channel switch announcement (CSA), when a mobile station receives invalid channel in CSA IE.
- 0.3%CVE-2024-38426Medium
While processing the authentication message in UE, improper authentication may lead to information disclosure.
- 0.2%CVE-2018-11922Critical
Wrong configuration in Touch Pal application can collect user behavior data without awareness by the user.
- 0.2%CVE-2019-2248High
Buffer overflow can occur if invalid header tries to overwrite the existing buffer which fix size allocation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...
- 0.2%CVE-2023-21629Medium
Memory Corruption in Modem due to double free while parsing the PKCS15 sim files.
- 0.1%CVE-2024-33042High
Memory corruption when Alternative Frequency offset value is set to 255.
- 0.1%CVE-2024-53014High
Memory corruption may occur while validating ports and channels in Audio driver.
- 0.1%CVE-2023-28575High
The cam_get_device_priv function does not check the type of handle being returned (device/session/link).
Running 215? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Weak Configuration due to improper input validation in Modem while processing LTE security mode command message received from network.
- Matched to
- 215 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 15 published vulnerabilities listed under the name 215, across 0 versions.
None of 215's vulnerabilities is on the list of flaws known to be exploited today.
Qualcomm also lists 215 under more specific names, such as 215 Firmware and 215 Mobile. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track 215. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.