Libx11 vulnerabilitiesRanked by how likely they are to be used.
Libx11 is made by X.org. We track 15 published vulnerabilities in it, across 66 versions. None of them is on the list of flaws known to be exploited today. If you run Libx11, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libx11 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libx11's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libx11 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.
- 11%CVE-2021-31535Critical
LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code.
- 9.3%CVE-2018-14600Critical
An issue was discovered in libX11 through 1.6.5.
- 4.8%CVE-2018-14599Critical
An issue was discovered in libX11 through 1.6.5.
- 4.6%CVE-2007-1667Critical
Multiple integer overflows in (1) the XGetPixel function in ImUtil.c in X.Org libx11 before 1.0.3, and (2) XInitImage function in xwd.c for ImageMagick, allow user-assisted remote attackers to cause a denial of...
- 4.5%CVE-2016-7942Critical
The XGetImage function in X.org libX11 before 1.6.4 might allow remote X servers to gain privileges via vectors involving image type and geometry, which triggers out-of-bounds read operations.
- 4.5%CVE-2016-7943Critical
The XListFonts function in X.org libX11 before 1.6.4 might allow remote X servers to gain privileges via vectors involving length fields, which trigger out-of-bounds write operations.
- 4.3%CVE-2013-7439High
Multiple off-by-one errors in the (1) MakeBigReq and (2) SetReqLen macros in include/X11/Xlibint.h in X11R6.x and libX11 before 1.6.0 allow remote attackers to have unspecified impact via a crafted request, which...
- 4.2%CVE-2018-14598High
An issue was discovered in XListExtensions in ListExt.c in libX11 through 1.6.5.
- 1.7%CVE-2023-3138High
A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the...
- 0.7%CVE-2023-43785Medium
A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function.
Running Libx11? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code. The libX11 XLookupColor request (intended for server-side color lookup) contains a flaw allowing a client to send color-name requests with a name longer than the maximum size allowed by the protocol (and also longer than the maximum packet size for normal-sized packets). The user-controlled data exceeding the maximum size is then interpreted by the server as additional X protocol requests and executed, e.g., to disable X server authorization completely. For example, if the victim encounters malicious terminal control sequences for color codes, then the attacker may be able to take full control of the running graphical session.
- Matched to
- Libx11 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 15 published vulnerabilities listed under the name Libx11, across 66 versions.
None of Libx11's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libx11. 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.