Libx11 Xorg Libx11

Do you want an email whenever new security vulnerabilities are reported in Xorg Libx11?

By the Year

In 2024 there have been 0 vulnerabilities in Xorg Libx11 . Last year Libx11 had 4 security vulnerabilities published. Right now, Libx11 is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 4 6.58
2022 0 0.00
2021 1 9.80
2020 2 7.25
2019 0 0.00
2018 3 9.03

It may take a day or so for new Libx11 vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Xorg Libx11 Security Vulnerabilities

A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function

CVE-2023-43785 5.5 - Medium - October 10, 2023

A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.

Out-of-bounds Read

A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function

CVE-2023-43787 7.8 - High - October 10, 2023

A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.

Integer Overflow or Wraparound

A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function

CVE-2023-43786 5.5 - Medium - October 10, 2023

A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.

Infinite Loop

A vulnerability was found in libX11

CVE-2023-3138 7.5 - High - June 28, 2023

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 arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.

Memory Corruption

LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code

CVE-2021-31535 9.8 - Critical - May 27, 2021

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.

Classic Buffer Overflow

An integer overflow vulnerability leading to a double-free was found in libX11

CVE-2020-14363 7.8 - High - September 11, 2020

An integer overflow vulnerability leading to a double-free was found in libX11. This flaw allows a local privileged attacker to cause an application compiled with libX11 to crash, or in some cases, result in arbitrary code execution. The highest threat from this flaw is to confidentiality, integrity as well as system availability.

Integer Overflow or Wraparound

An integer overflow leading to a heap-buffer overflow was found in The X Input Method (XIM) client was implemented in libX11 before version 1.6.10

CVE-2020-14344 6.7 - Medium - August 05, 2020

An integer overflow leading to a heap-buffer overflow was found in The X Input Method (XIM) client was implemented in libX11 before version 1.6.10. As per upstream this is security relevant when setuid programs call XIM client functions while running with elevated privileges. No such programs are shipped with Red Hat Enterprise Linux.

Integer Overflow or Wraparound

An issue was discovered in XListExtensions in ListExt.c in libX11 through 1.6.5

CVE-2018-14598 7.5 - High - August 24, 2018

An issue was discovered in XListExtensions in ListExt.c in libX11 through 1.6.5. A malicious server can send a reply in which the first string overflows, causing a variable to be set to NULL that will be freed later on, leading to DoS (segmentation fault).

Improper Input Validation

An issue was discovered in libX11 through 1.6.5

CVE-2018-14599 9.8 - Critical - August 24, 2018

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c is vulnerable to an off-by-one error caused by malicious server responses, leading to DoS or possibly unspecified other impact.

off-by-five

An issue was discovered in libX11 through 1.6.5

CVE-2018-14600 9.8 - Critical - August 24, 2018

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c interprets a variable as signed instead of unsigned, resulting in an out-of-bounds write (of up to 128 bytes), leading to DoS or remote code execution.

Memory Corruption

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Debian Linux or by Xorg? Click the Watch button to subscribe.

Xorg
Vendor

Xorg Libx11
Product

subscribe