FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-03-27 18:04:16 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

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

VuXML IDDescription
ddecde18-e33b-11e7-a293-54e1ad3d6335libXcursor -- integer overflow that can lead to heap buffer overflow

The freedesktop.org project reports:

It is possible to trigger heap overflows due to an integer overflow while parsing images and a signedness issue while parsing comments.

The integer overflow occurs because the chosen limit 0x10000 for dimensions is too large for 32 bit systems, because each pixel takes 4 bytes. Properly chosen values allow an overflow which in turn will lead to less allocated memory than needed for subsequent reads.

The signedness bug is triggered by reading the length of a comment as unsigned int, but casting it to int when calling the function XcursorCommentCreate. Turning length into a negative value allows the check against XCURSOR_COMMENT_MAX_LEN to pass, and the following addition of sizeof (XcursorComment) + 1 makes it possible to allocate less memory than needed for subsequent reads.


Discovery 2017-11-28
Entry 2017-12-17
libXcursor
< 1.1.15

http://seclists.org/oss-sec/2017/q4/339
https://cgit.freedesktop.org/xorg/lib/libXcursor/commit/?id=4794b5dd34688158fb51a2943032569d3780c4b8
CVE-2017-16612
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
< 1.6.0

libXext
< 1.3.2

libXfixes
< 5.0.1

libXi
< 1.7_1

libXinerama
< 1.1.3

libXp
< 1.0.2

libXrandr
< 1.4.1

libXrender
< 0.9.7_1

libXres
< 1.0.7

libXtst
< 1.2.2

libXv
< 1.0.8

libXvMC
< 1.0.7_1

libXxf86dga
< 1.1.4

libdmx
< 1.1.3

libxcb
< 1.9.1

libGL
< 7.6.1_4

gt 7.8.0 lt 8.0.5_4

xf86-video-openchrome
< 0.3.3

libFS
< 1.0.5

libXxf86vm
< 1.1.3

libXt
< 1.1.4

libXcursor
< 1.1.14

CVE-2013-1992
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-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