https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:49:40 +0000 https://cve.radiocsirt.org/vuln/cnvd-2017-02392 cnvd-2017-02392 https://cve.radiocsirt.org/vuln/cnvd-2017-02392 https://cve.radiocsirt.org/vuln/euvd-2026-72432 EUVD-2026-72432 https://cve.radiocsirt.org/vuln/euvd-2026-72432 https://cve.radiocsirt.org/vuln/fkie_cve-2017-2624 <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-2624 https://cve.radiocsirt.org/vuln/ghsa-6pw7-qhf8-rjff <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> https://cve.radiocsirt.org/vuln/ghsa-6pw7-qhf8-rjff https://cve.radiocsirt.org/vuln/gsd-2017-2624 gsd-2017-2624 https://cve.radiocsirt.org/vuln/gsd-2017-2624 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11525-1 <p>xorg-x11-server-1.20.13-1.2 on GA media</p> <p>xorg-x11-server-1.20.13-1.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11525-1 https://cve.radiocsirt.org/vuln/suse-su-2017:1675-1 <p>Security update for xorg-x11-server</p> <p>Security update for xorg-x11-server</p> https://cve.radiocsirt.org/vuln/suse-su-2017:1675-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-2624 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: xorg-server, Ubuntu:14.04:LTS: xorg-server-lts-xenial, Ubuntu:16.04:LTS: xorg-server, Ubuntu:16.04:LTS: xorg-server-hwe-16.04</p> <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: xorg-server, Ubuntu:14.04:LTS: xorg-server-lts-xenial, Ubuntu:16.04:LTS: xorg-server, Ubuntu:16.04:LTS: xorg-server-hwe-16.04</p> <p>It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-2624