Apq8037 Firmware vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Apq8037 Firmware is made by Qualcomm. We track 97 published vulnerabilities in it, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 1 December 2021. If you run Apq8037 Firmware, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Apq8037 Firmware flaw added to the known-exploited list is CVE-2020-11261, on 1 December 2021. We keep watching the known-exploited list.

Versions

Which versions of Apq8037 Firmware do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

Known exploited

Which Apq8037 Firmware vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2020-11261HighKnown exploited
    Qualcomm Multiple Chipsets Improper Input Validation Vulnerability

    Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,...

    Chance of use1.6%Known exploited since1 Dec 2021
Exploit likelihood

Which Apq8037 Firmware 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%
    CVE-2020-11261HighKnown exploited

    Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,...

    CVSS7.8Published9 Jun 2021
  2. 1.1%

    Out of bound write while parsing SDP string due to missing check on null termination in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon...

    CVSS9.8Published17 Mar 2021
  3. 1.0%

    Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.1Published17 Mar 2021
  4. 1.0%

    Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.1Published17 Mar 2021
  5. 1.0%

    Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.1Published17 Mar 2021
  6. 1.0%

    Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.1Published17 Mar 2021
  7. 0.9%

    Out of bound read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS9.1Published7 Apr 2021
  8. 0.9%

    Out of bound memory read while unpacking data due to lack of offset length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT,...

    CVSS9.1Published7 Apr 2021
  9. 0.9%

    Out-of-bounds read vulnerability while accessing DTMF payload due to lack of check of buffer length before copying in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon...

    CVSS9.1Published7 Apr 2021
  10. 0.9%

    Potential out of bound read exception when UE receives unusually large number of padding octets in the beginning of ROHC header in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer...

    CVSS9.1Published17 Mar 2021
Precursor Intelligence

Running Apq8037 Firmware? 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 97 published vulnerabilities listed under the name Apq8037 Firmware, across 0 versions. The most recent Apq8037 Firmware flaw added to the known-exploited list is CVE-2020-11261, on 1 December 2021.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-11261.

Create a Precursor Intelligence account and track Apq8037 Firmware. 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.