Libxi vulnerabilitiesRanked by how likely they are to be used.

Product18 versions
The short answer

Libxi is made by X.org. We track 5 published vulnerabilities in it, across 18 versions. None of them is on the list of flaws known to be exploited today. If you run Libxi, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Libxi vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Libxi 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. 3.0%

    X.org libXi before 1.7.7 allows remote X servers to cause a denial of service (infinite loop) via vectors involving length fields.

    CVSS7.5Published13 Dec 2016
  2. 3.0%

    Multiple integer overflows in X.org libXi before 1.7.7 allow remote X servers to cause a denial of service (out-of-bounds memory access or infinite loop) via vectors involving length fields.

    CVSS7.5Published13 Dec 2016
  3. 2.8%

    Multiple buffer overflows in X.org libXi 1.7.1 and earlier allow X servers to cause a denial of service (crash) and possibly execute arbitrary code via crafted length or index values to the (1)...

    CVSS6.8Published15 Jun 2013
  4. 1.9%

    X.org libXi 1.7.1 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to an unexpected sign extension in the XListInputDevices function.

    CVSS6.8Published15 Jun 2013
  5. 1.8%

    Multiple integer overflows in X.org libXi 1.7.1 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the (1) XGetDeviceControl, (2)...

    CVSS6.8Published15 Jun 2013
Precursor Intelligence

Running Libxi? 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 5 published vulnerabilities listed under the name Libxi, across 18 versions.

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

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