Libxfont vulnerabilitiesRanked by how likely they are to be used.

Product3 versions
The short answer

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

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Libxfont vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Libxfont 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. 5.6%

    Integer overflow in the bdfReadCharacters function in bdfread.c in (1) X.Org libXfont before 20070403 and (2) freetype 2.3.2 and earlier allows remote authenticated users to execute arbitrary code via crafted BDF...

    CVSS8.5Published6 Apr 2007
  2. 1.5%

    Integer overflow in the FontFileInitTable function in X.Org libXfont before 20070403 allows remote authenticated users to execute arbitrary code via a long first line in the fonts.dir file, which results in a heap...

    CVSS3.8Published6 Apr 2007
  3. 0.4%

    In the PatternMatch function in fontfile/fontdir.c in libXfont through 1.5.2 and 2.x before 2.0.2, an attacker with access to an X connection can cause a buffer over-read during pattern matching of fonts, leading to...

    CVSS7.1Published11 Oct 2017
  4. 0.4%

    In the pcfGetProperties function in bitmap/pcfread.c in libXfont through 1.5.2 and 2.x before 2.0.2, a missing boundary check (for PCF files) could be used by local attackers authenticated to an Xserver for a buffer...

    CVSS7.1Published11 Oct 2017
Precursor Intelligence

Running Libxfont? 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 4 published vulnerabilities listed under the name Libxfont, across 3 versions.

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

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