https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 01:59:31 +0000 https://cve.radiocsirt.org/vuln/alsa-2021:4385 <p><strong>Affected:</strong> AlmaLinux:8: glib2-doc, AlmaLinux:8: glib2-static</p> <p>GLib provides the core application building blocks for libraries and applications written in C. It provides the core object system used in GNOME, the main loop implementation, and a large set of utility functions for strings and common data structures.</p> <p>Security Fix(es):</p> <p>* glib2: Possible privilege escalation thourgh pkexec and aliases (CVE-2021-3800)</p> <p>* glib: g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION creates empty target for dangling symlink (CVE-2021-28153)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p>Additional Changes:</p> <p>For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.</p> <p><strong>Affected:</strong> AlmaLinux:8: glib2-doc, AlmaLinux:8: glib2-static</p> <p>GLib provides the core application building blocks for libraries and applications written in C. It provides the core object system used in GNOME, the main loop implementation, and a large set of utility functions for strings and common data structures.</p> <p>Security Fix(es):</p> <p>* glib2: Possible privilege escalation thourgh pkexec and aliases (CVE-2021-3800)</p> <p>* glib: g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION creates empty target for dangling symlink (CVE-2021-28153)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p>Additional Changes:</p> <p>For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2021:4385 https://cve.radiocsirt.org/vuln/bdu:2022-00320 bdu:2022-00320 https://cve.radiocsirt.org/vuln/bdu:2022-00320 https://cve.radiocsirt.org/vuln/bell-cve-2021-28153 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2021-28153 https://cve.radiocsirt.org/vuln/certfr-2022-avi-386 certfr-2022-avi-386 https://cve.radiocsirt.org/vuln/certfr-2022-avi-386 https://cve.radiocsirt.org/vuln/euvd-2026-25866 EUVD-2026-25866 https://cve.radiocsirt.org/vuln/euvd-2026-25866 https://cve.radiocsirt.org/vuln/fkie_cve-2021-28153 <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-28153 https://cve.radiocsirt.org/vuln/ghsa-9hh6-p5c5-mmmf <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> https://cve.radiocsirt.org/vuln/ghsa-9hh6-p5c5-mmmf https://cve.radiocsirt.org/vuln/gsd-2021-28153 gsd-2021-28153 https://cve.radiocsirt.org/vuln/gsd-2021-28153 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/msrc_cve-2021-28153 msrc_CVE-2021-28153 https://cve.radiocsirt.org/vuln/msrc_cve-2021-28153 https://cve.radiocsirt.org/vuln/oesa-2021-1164 <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: glib2</p> <p>GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib&amp;apos;s code was separated from GTK, so it can be used by software other than GNOME and has been developed in parallel ever since. Security Fix(es): An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)(CVE-2021-28153)</p> <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: glib2</p> <p>GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib&amp;apos;s code was separated from GTK, so it can be used by software other than GNOME and has been developed in parallel ever since. Security Fix(es): An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)(CVE-2021-28153)</p> https://cve.radiocsirt.org/vuln/oesa-2021-1164 https://cve.radiocsirt.org/vuln/rhsa-2021:4385 <p>glib2: Possible privilege escalation thourgh pkexec and aliases glib: g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION creates empty target for dangling symlink</p> <p>glib2: Possible privilege escalation thourgh pkexec and aliases glib: g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION creates empty target for dangling symlink</p> https://cve.radiocsirt.org/vuln/rhsa-2021:4385 https://cve.radiocsirt.org/vuln/suse-su-2022:1455-1 <p>Security update for glib2</p> <p>Security update for glib2</p> https://cve.radiocsirt.org/vuln/suse-su-2022:1455-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-28153 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: glib2.0, Ubuntu:16.04:LTS: glib2.0, Ubuntu:18.04:LTS: glib2.0, Ubuntu:20.04:LTS: glib2.0</p> <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: glib2.0, Ubuntu:16.04:LTS: glib2.0, Ubuntu:18.04:LTS: glib2.0, Ubuntu:20.04:LTS: glib2.0</p> <p>An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-28153 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0089 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GNOME ausnutzen, um Dateien zu manipulieren.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GNOME ausnutzen, um Dateien zu manipulieren.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0089