Package Hub vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Package Hub is made by Suse. We track 39 published vulnerabilities in it, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 8 June 2022. If you run Package Hub, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Package Hub flaw added to the known-exploited list is CVE-2016-1646, on 8 June 2022. We keep watching the known-exploited list.

Versions

Which versions of Package Hub 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 Package Hub 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. 8.8
    CVE-2016-1646HighKnown exploited
    Google Chromium V8 Out-of-Bounds Read Vulnerability

    Google Chromium V8 Engine contains an out-of-bounds read vulnerability that allows a remote attacker to cause a denial of service or possibly have another unspecified impact via crafted JavaScript code.

    Chance of use48%Known exploited since8 Jun 2022
Exploit likelihood

Which Package Hub 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. 48%
    CVE-2016-1646HighKnown exploited

    The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, does not properly consider element data types, which allows remote attackers to cause a denial of...

    CVSS8.8Published29 Mar 2016
  2. 20%

    A vulnerability exists where if a user opens a locally saved HTML file, this file can use file: URIs to access other files in the same directory or sub-directories if the names are known or guessed.

    CVSS6.5Published23 Jul 2019
  3. 8.0%

    multiSelect in select.c in SQLite 3.30.1 mishandles certain errors during parsing, as demonstrated by errors from sqlite3WindowRewrite() calls.

    CVSS7.5Published23 Dec 2019
  4. 6.9%

    exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled.

    CVSS7.5Published18 Dec 2019
  5. 6.8%

    flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view.

    CVSS7.5Published24 Dec 2019
  6. 6.8%

    zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.

    CVSS7.5Published24 Dec 2019
  7. 6.4%

    Type confusion in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

    CVSS8.8Published10 Dec 2019
  8. 3.9%

    Out of bounds write in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

    CVSS8.8Published10 Dec 2019
  9. 3.3%

    Icinga Icinga Web2 2.0.0 through 2.6.4, 2.7.4 and 2.8.2 has a Directory Traversal vulnerability which allows an attacker to access arbitrary files that are readable by the process running Icinga Web 2.

    CVSS7.5Published19 Aug 2020
  10. 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
Precursor Intelligence

Running Package Hub? 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 39 published vulnerabilities listed under the name Package Hub, across 0 versions. The most recent Package Hub flaw added to the known-exploited list is CVE-2016-1646, on 8 June 2022.

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

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