FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

Revision:  517704
Date:      2019-11-15
Time:      22:46:16Z
Committer: naddy

List all Vulnerabilities, by package

List all Vulnerabilities, by date

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
2eebebff-cd3b-11e2-8f09-001b38c3836cxorg -- protocol handling issues in X Window System client libraries

freedesktop.org reports:

Ilja van Sprundel, a security researcher with IOActive, has discovered a large number of issues in the way various X client libraries handle the responses they receive from servers, and has worked with X.Org's security team to analyze, confirm, and fix these issues.

Most of these issues stem from the client libraries trusting the server to send correct protocol data, and not verifying that the values will not overflow or cause other damage. Most of the time X clients & servers are run by the same user, with the server more privileged from the clients, so this is not a problem, but there are scenarios in which a privileged client can be connected to an unprivileged server, for instance, connecting a setuid X client (such as a screen lock program) to a virtual X server (such as Xvfb or Xephyr) which the user has modified to return invalid data, potentially allowing the user to escalate their privileges.

The vulnerabilities include:

Integer overflows calculating memory needs for replies.

Sign extension issues calculating memory needs for replies.

Buffer overflows due to not validating length or offset values in replies.

Integer overflows parsing user-specified files.

Unbounded recursion parsing user-specified files.

Memory corruption due to unchecked return values.


Discovery 2013-05-23
Entry 2013-06-04
libX11
lt 1.6.0

libXext
lt 1.3.2

libXfixes
lt 5.0.1

libXi
lt 1.7_1

libXinerama
lt 1.1.3

libXp
lt 1.0.2

libXrandr
lt 1.4.1

libXrender
lt 0.9.7_1

libXres
lt 1.0.7

libXtst
lt 1.2.2

libXv
lt 1.0.8

libXvMC
lt 1.0.7_1

libXxf86dga
lt 1.1.4

libdmx
lt 1.1.3

libxcb
lt 1.9.1

libGL
lt 7.6.1_4

gt 7.8.0 lt 8.0.5_4

xf86-video-openchrome
lt 0.3.3

libFS
lt 1.0.5

libXxf86vm
lt 1.1.3

libXt
lt 1.1.4

libXcursor
lt 1.1.14

CVE-2013-1981
CVE-2013-1982
CVE-2013-1983
CVE-2013-1984
CVE-2013-1985
CVE-2013-1986
CVE-2013-1987
CVE-2013-1988
CVE-2013-1989
CVE-2013-1990
CVE-2013-1991
CVE-2013-1992
CVE-2013-1993
CVE-2013-1994
CVE-2013-1995
CVE-2013-1996
CVE-2013-1997
CVE-2013-1998
CVE-2013-1999
CVE-2013-2000
CVE-2013-2001
CVE-2013-2002
CVE-2013-2003
CVE-2013-2004
CVE-2013-2005
CVE-2013-2062
CVE-2013-2063
CVE-2013-2064
CVE-2013-2066
fe99d3ca-a63a-11e8-a7c6-54e1ad3d6335libX11 -- Multiple vulnerabilities

The freedesktop.org project reports:

The functions XGetFontPath, XListExtensions, and XListFonts are vulnerable to an off-by-one override on malicious server responses. The server replies consist of chunks consisting of a length byte followed by actual string, which is not NUL-terminated. While parsing the response, the length byte is overridden with '\0', thus the memory area can be used as storage of C strings later on. To be able to NUL-terminate the last string, the buffer is reserved with an additional byte of space. For a boundary check, the variable chend (end of ch) was introduced, pointing at the end of the buffer which ch initially points to. Unfortunately there is a difference in handling "the end of ch". While chend points at the first byte that must not be written to, the for-loop uses chend as the last byte that can be written to. Therefore, an off-by-one can occur.

The length value is interpreted as signed char on many systems (depending on default signedness of char), which can lead to an out of boundary write up to 128 bytes in front of the allocated storage, but limited to NUL byte(s).

If the server sends a reply in which even the first string would overflow the transmitted bytes, list[0] (or flist[0]) will be set to NULL and a count of 0 is returned. If the resulting list is freed with XFreeExtensionList or XFreeFontPath later on, the first Xfree call is turned into Xfree (NULL-1) which will most likely trigger a segmentation fault. Casting the length value to unsigned char fixes the problem and allows string values with up to 255 characters.


Discovery 2018-08-21
Entry 2018-08-22
libX11
lt 1.6.6,1

CVE-2018-14599
https://lists.x.org/archives/xorg-announce/2018-August/002915.html
CVE-2018-14598
CVE-2018-14600
1cf65085-a760-41d2-9251-943e1af62eb8X.org libraries -- multiple vulnerabilities

Matthieu Herrb reports:

Tobias Stoeckmann from the OpenBSD project has discovered a number of issues in the way various X client libraries handle the responses they receive from servers, and has worked with X.Org's security team to analyze, confirm, and fix these issues. These issue come in addition to the ones discovered by Ilja van Sprundel in 2013.

Most of these issues stem from the client libraries trusting the server to send correct protocol data, and not verifying that the values will not overflow or cause other damage. Most of the time X clients and servers are run by the same user, with the server more privileged than the clients, so this is not a problem, but there are scenarios in which a privileged client can be connected to an unprivileged server, for instance, connecting a setuid X client (such as a screen lock program) to a virtual X server (such as Xvfb or Xephyr) which the user has modified to return invalid data, potentially allowing the user to escalate their privileges.


Discovery 2016-10-04
Entry 2016-10-07
Modified 2016-10-10
libX11
lt 1.6.4,1

libXfixes
lt 5.0.3

libXi
lt 1.7.7,1

libXrandr
lt 1.5.1

libXrender
lt 0.9.10

libXtst
lt 1.2.3

libXv
lt 1.0.11,1

libXvMC
lt 1.0.10

https://lists.x.org/archives/xorg-announce/2016-October/002720.html
CVE-2016-5407