https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:07:00 +0000 https://cve.radiocsirt.org/vuln/certfr-2021-avi-589 certfr-2021-avi-589 https://cve.radiocsirt.org/vuln/certfr-2021-avi-589 https://cve.radiocsirt.org/vuln/cnvd-2021-01285 cnvd-2021-01285 https://cve.radiocsirt.org/vuln/cnvd-2021-01285 https://cve.radiocsirt.org/vuln/euvd-2026-47357 EUVD-2026-47357 https://cve.radiocsirt.org/vuln/euvd-2026-47357 https://cve.radiocsirt.org/vuln/fkie_cve-2020-29573 <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf. NOTE: the issue does not affect glibc by default in 2016 or later (i.e., 2.23 or later) because of commits made in 2015 for inlining of C99 math functions through use of GCC built-ins. In other words, the reference to 2.23 is intentional despite the mention of &#34;Fixed for glibc 2.33&#34; in the 26649 reference.</p> <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf. NOTE: the issue does not affect glibc by default in 2016 or later (i.e., 2.23 or later) because of commits made in 2015 for inlining of C99 math functions through use of GCC built-ins. In other words, the reference to 2.23 is intentional despite the mention of &#34;Fixed for glibc 2.33&#34; in the 26649 reference.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-29573 https://cve.radiocsirt.org/vuln/ghsa-x6gp-hg9r-wh46 <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf.</p> <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf.</p> https://cve.radiocsirt.org/vuln/ghsa-x6gp-hg9r-wh46 https://cve.radiocsirt.org/vuln/gsd-2020-29573 gsd-2020-29573 https://cve.radiocsirt.org/vuln/gsd-2020-29573 https://cve.radiocsirt.org/vuln/icsa-23-348-10 <p>expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE. shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename. In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start o…</p> <p>expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE. shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename. In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start o…</p> https://cve.radiocsirt.org/vuln/icsa-23-348-10 https://cve.radiocsirt.org/vuln/opensuse-su-2021:0358-1 <p>Security update for glibc</p> <p>Security update for glibc</p> https://cve.radiocsirt.org/vuln/opensuse-su-2021:0358-1 https://cve.radiocsirt.org/vuln/rhsa-2021:0949 <p>expat: large number of colons in input makes parser consume high amount of resources, leading to DoS e2fsprogs: Crafted ext4 partition leads to out-of-bounds write e2fsprogs: Out-of-bounds write in e2fsck/rehash.c curl: heap buffer overflow in function tftp_receive_packet() nss: Out-of-bounds read when importing curve25519 private key nss: PKCS#1 v1.5 signatures can be used for TLS 1.3 nss: Use-after-free in sftk_FreeSession due to improper refcounting glib2: file_copy_fallback in gio/gfile.c in GNOME GLib does not properly restrict file permissions while a copy operation is in progress dbus: DBusServer DBUS_COOKIE_SHA1 authentication bypass ibus: missing authorization allows local attacker to access the input bus of another user cpio: improper input validation when writing tar header fields leads to unexpected tar generation expat: heap-based buffer over-read via crafted XML input python: XSS vulnerability in the documentation XML-RPC server in server_title field nss: Check length of inputs for cryptographic primitives nss: TLS 1.3 HelloRetryRequest downgrade request sets client into invalid state libssh2: integer overflow in SSH_MSG_DISCONNECT logic in packet.c glibc: LD_PREFER_MAP_32BIT_EXEC not ignored in setuid binaries libxml2: memory leak in xmlParseBalancedChunkMemoryRecover in parser.c systemd: memory leak in button_open() in login/logind-button.c when udev events are received libxml2: memory leak in xmlSchemaPreRun in xmlschemas.c python: infinite loop in the tarfi…</p> <p>expat: large number of colons in input makes parser consume high amount of resources, leading to DoS e2fsprogs: Crafted ext4 partition leads to out-of-bounds write e2fsprogs: Out-of-bounds write in e2fsck/rehash.c curl: heap buffer overflow in function tftp_receive_packet() nss: Out-of-bounds read when importing curve25519 private key nss: PKCS#1 v1.5 signatures can be used for TLS 1.3 nss: Use-after-free in sftk_FreeSession due to improper refcounting glib2: file_copy_fallback in gio/gfile.c in GNOME GLib does not properly restrict file permissions while a copy operation is in progress dbus: DBusServer DBUS_COOKIE_SHA1 authentication bypass ibus: missing authorization allows local attacker to access the input bus of another user cpio: improper input validation when writing tar header fields leads to unexpected tar generation expat: heap-based buffer over-read via crafted XML input python: XSS vulnerability in the documentation XML-RPC server in server_title field nss: Check length of inputs for cryptographic primitives nss: TLS 1.3 HelloRetryRequest downgrade request sets client into invalid state libssh2: integer overflow in SSH_MSG_DISCONNECT logic in packet.c glibc: LD_PREFER_MAP_32BIT_EXEC not ignored in setuid binaries libxml2: memory leak in xmlParseBalancedChunkMemoryRecover in parser.c systemd: memory leak in button_open() in login/logind-button.c when udev events are received libxml2: memory leak in xmlSchemaPreRun in xmlschemas.c python: infinite loop in the tarfi…</p> https://cve.radiocsirt.org/vuln/rhsa-2021:0949 https://cve.radiocsirt.org/vuln/suse-su-2021:0653-1 <p>Security update for glibc</p> <p>Security update for glibc</p> https://cve.radiocsirt.org/vuln/suse-su-2021:0653-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-29573 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: eglibc</p> <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf. NOTE: the issue does not affect glibc by default in 2016 or later (i.e., 2.23 or later) because of commits made in 2015 for inlining of C99 math functions through use of GCC built-ins. In other words, the reference to 2.23 is intentional despite the mention of &#34;Fixed for glibc 2.33&#34; in the 26649 reference.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: eglibc</p> <p>sysdeps/i386/ldbl2mpn.c in the GNU C Library (aka glibc or libc6) before 2.23 on x86 targets has a stack-based buffer overflow if the input to any of the printf family of functions is an 80-bit long double with a non-canonical bit pattern, as seen when passing a \x00\x04\x00\x00\x00\x00\x00\x00\x00\x04 value to sprintf. NOTE: the issue does not affect glibc by default in 2016 or later (i.e., 2.23 or later) because of commits made in 2015 for inlining of C99 math functions through use of GCC built-ins. In other words, the reference to 2.23 is intentional despite the mention of &#34;Fixed for glibc 2.33&#34; in the 26649 reference.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-29573 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1169 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in GNU libc ausnutzen, um einen Denial of Service Angriff durchzuführen oder Code zur Ausführung zu bringen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in GNU libc ausnutzen, um einen Denial of Service Angriff durchzuführen oder Code zur Ausführung zu bringen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1169