https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:10:21 +0000 https://cve.radiocsirt.org/vuln/bdu:2016-02233 bdu:2016-02233 https://cve.radiocsirt.org/vuln/bdu:2016-02233 https://cve.radiocsirt.org/vuln/euvd-2026-107706 EUVD-2026-107706 https://cve.radiocsirt.org/vuln/euvd-2026-107706 https://cve.radiocsirt.org/vuln/fkie_cve-2013-4788 <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2013-4788 https://cve.radiocsirt.org/vuln/ghsa-xh2f-h76w-4qqc <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> https://cve.radiocsirt.org/vuln/ghsa-xh2f-h76w-4qqc https://cve.radiocsirt.org/vuln/gsd-2013-4788 gsd-2013-4788 https://cve.radiocsirt.org/vuln/gsd-2013-4788 https://cve.radiocsirt.org/vuln/suse-ru-2015:0794-1 <p>Security update for glibc</p> <p>Security update for glibc</p> https://cve.radiocsirt.org/vuln/suse-ru-2015:0794-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2013-4788 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: eglibc</p> <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: eglibc</p> <p>The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2013-4788