Mdm9207c vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Mdm9207c is made by Qualcomm. We track 118 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 Mdm9207c Firmware, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Mdm9207c listed under other names? Yes.

Qualcomm also lists Mdm9207c under more specific names, such as Mdm9207c Firmware. 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.

Known exploited

Which Mdm9207c vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Mdm9207c's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Mdm9207c 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.

50% or more10% to 49%Under 10%
  1. 1.6%

    Lack of boundary checks for data offsets received from HLOS can lead to out-of-bound read in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS7.1Published16 Apr 2020
  2. 1.1%

    NULL is assigned to local instance of audio device pointer after free instead of global static pointer and can lead to use after free issue in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT,...

    CVSS9.8Published21 Jan 2020
  3. 1.1%

    Array out of bound may occur while playing mp3 file as no check is there on offset if it is greater than the buffer allocated or not in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.8Published2 Jun 2020
  4. 1.1%

    Integer overflow may occur if atom size is less than atom offset as there is improper validation of atom size in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon...

    CVSS9.8Published2 Jun 2020
  5. 1.0%

    Buffer overflow occur while playing the clip which is nonstandard due to lack of offset length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial...

    CVSS9.8Published21 Jan 2020
  6. 1.0%

    Buffer overflow occur while playing the clip which is nonstandard due to lack of check of size duration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial...

    CVSS9.8Published21 Jan 2020
Precursor Intelligence

Running Mdm9207c? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 118 published vulnerabilities listed under the name Mdm9207c, across 0 versions.

None of Mdm9207c's vulnerabilities is on the list of flaws known to be exploited today.

Qualcomm also lists Mdm9207c under more specific names, such as Mdm9207c Firmware. 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 Mdm9207c. 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.