aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/config
diff options
context:
space:
mode:
authorKees Cook <kees@outflux.net>2013-06-09 11:13:42 -0700
committerUlrich Sibiller <uli42@gmx.de>2016-10-19 21:40:28 +0200
commitea8239650656846d810a93e7659e182e412f07b3 (patch)
treefe420308c8107eeccfe75162f92d568129185866 /nx-X11/config
parent39c6e5aa859c633fcb48e299643bb0189f333a0d (diff)
downloadnx-libs-ea8239650656846d810a93e7659e182e412f07b3.tar.gz
nx-libs-ea8239650656846d810a93e7659e182e412f07b3.tar.bz2
nx-libs-ea8239650656846d810a93e7659e182e412f07b3.zip
libX11: check size of GetReqExtra after XFlush
Two users of GetReqExtra pass arbitrarily sized allocations from the caller (ModMap and Host). Adjust _XGetRequest() (called by the GetReqExtra macro) to double-check the requested length and invalidate "req" when this happens. Users of GetReqExtra passing lengths greater than the Xlib buffer size (normally 16K) must check "req" and fail gracefully instead of crashing. Any callers of GetReqExtra that do not check "req" for NULL will experience this change, in the pathological case, as a NULL dereference instead of a buffer overflow. This is an improvement, but the documentation for GetReqExtra has been updated to reflect the need to check the value of "req" after the call. Bug that manifested the problem: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/792628 Signed-off-by: Kees Cook <kees@outflux.net> Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com> Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com> Backported-to-NX-by: Ulrich Sibiller <uli42@gmx.de>
Diffstat (limited to 'nx-X11/config')
0 files changed, 0 insertions, 0 deletions