File _patchinfo of Package patchinfo.8102

<patchinfo incident="8102">
  <issue id="1102062" tracker="bnc">VUL-0: EMBARGOED: CVE-2018-14599: libX11,xorg-x11-libX11, xorg-x11: off-by-one write in XListExtensions</issue>
  <issue id="1102068" tracker="bnc">VUL-0: EMBARGOED: CVE-2018-14600: libX11,xorg-x11-libX11, xorg-x11: out of boundary write in XListExtensions</issue>
  <issue id="1102073" tracker="bnc">VUL-0: EMBARGOED: CVE-2018-14598: libX11,xorg-x11-libX11, xorg-x11: crash on invalid reply in XListExtensions</issue>
  <issue id="2018-14598" tracker="cve" />
  <issue id="2018-14599" tracker="cve" />
  <issue id="2018-14600" tracker="cve" />
  <issue tracker="bnc" id="1094327">X-clients exit with XIOError, libX11 issue</issue>
  <category>security</category>
  <rating>moderate</rating>
  <packager>vliaskovitis</packager>
  <description>This update for libX11 and libxcb fixes the following issue:

libX11:

These security issues were fixed:

- CVE-2018-14599: The function XListExtensions was vulnerable to an off-by-one
  error caused by malicious server responses, leading to DoS or possibly
  unspecified other impact (bsc#1102062).
- CVE-2018-14600: The function XListExtensions interpreted 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 (bsc#1102068).
- CVE-2018-14598: A malicious server could have sent 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) (bsc#1102073).

This non-security issue was fixed:

- Make use of the new 64-bit sequence number API in XCB 1.11.1 to avoid the 32-bit
  sequence number wrap in libX11 (bsc#1094327).

libxcb:

- Expose 64-bit sequence number from XCB API so that Xlib and others can use it even
  on 32-bit environment. (bsc#1094327)
</description>
  <summary>Security update for libX11 and libxcb</summary>
</patchinfo>