Backports vulnerabilitiesRanked by how likely they are to be used.

Product1 versions
The short answer

Backports is made by Opensuse. We track 97 published vulnerabilities listed under that exact name, across 1 version. None of them is on the list of flaws known to be exploited today. Opensuse lists newer releases under their own names, such as Backports Sle, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Backports listed under other names? Yes.

Opensuse also lists Backports under more specific names, such as Backports Sle. 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 Backports vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Backports 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. 32%

    Zabbix before 3.0.32rc1, 4.x before 4.0.22rc1, 4.1.x through 4.4.x before 4.4.10rc1, and 5.x before 5.0.2rc1 allows stored XSS in the URL Widget.

    CVSS6.1Published17 Jul 2020
  2. 9.3%

    An integer overflow that leads to a use-after-free in WebMIDI in Google Chrome on Windows prior to 73.0.3683.75 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a...

    CVSS8.8Published23 May 2019
  3. 9.1%

    An integer overflow that leads to a use-after-free in Blink Storage in Google Chrome on Linux prior to 73.0.3683.75 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a...

    CVSS8.8Published23 May 2019
  4. 7.9%

    rdesktop versions up to and including v1.8.3 contain an Integer Overflow that leads to a Heap-Based Buffer Overflow in the function rdp_in_unistr() and results in memory corruption and possibly even a remote code...

    CVSS9.8Published15 Mar 2019
  5. 5.4%

    GraphicsMagick before 1.3.35 has an integer overflow and resultant heap-based buffer overflow in HuffmanDecodeImage in magick/compress.c.

    CVSS9.8Published24 Mar 2020
  6. 3.4%

    An issue was discovered in Qt before 5.11.3.

    CVSS9.8Published26 Dec 2018
  7. 3.2%

    Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (CPU consumption), aka TROVE-2020-002.

    CVSS7.5Published23 Mar 2020
  8. 3.2%

    Lack of correct bounds checking in Skia in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

    CVSS6.5Published23 May 2019
  9. 2.8%

    ImageMagick 7.0.8-35 has a memory leak in coders/dps.c, as demonstrated by XCreateImage.

    CVSS6.5Published23 Sep 2019
  10. 2.8%

    An Integer underflow in VLC Media Player versions < 3.0.7 leads to an out-of-band read.

    CVSS7.1Published30 Jul 2019
Precursor Intelligence

Running Backports? 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 Backports, across 1 version.

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

Opensuse also lists Backports under more specific names, such as Backports Sle. 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 Backports. 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.