GNOME Glib 2.66.7

CPE Details

GNOME Glib 2.66.7
gnome
glib
2.66.7
2021-02-22
12h36 +00:00
2021-03-26
16h25 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:gnome:glib:2.66.7:*:*:*:*:*:*:*

Informations

Vendor

gnome

Product

glib

Version

2.66.7

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-32636 2023-09-14 19h19 +00:00 A flaw was found in glib, where the gvariant deserialization code is vulnerable to a denial of service introduced by additional input validation added to resolve CVE-2023-29499. The offset table validation may be very slow. This bug does not affect any released version of glib but does affect glib distributors who followed the guidance of glib developers to backport the initial fix for CVE-2023-29499.
7.5
High
CVE-2023-32643 2023-09-14 19h14 +00:00 A flaw was found in GLib. The GVariant deserialization code is vulnerable to a heap buffer overflow introduced by the fix for CVE-2023-32665. This bug does not affect any released version of GLib, but does affect GLib distributors who followed the guidance of GLib developers to backport the initial fix for CVE-2023-32665.
7.8
High
CVE-2023-32611 2023-09-14 19h07 +00:00 A flaw was found in GLib. GVariant deserialization is vulnerable to a slowdown issue where a crafted GVariant can cause excessive processing, leading to denial of service.
5.5
Medium
CVE-2023-29499 2023-09-14 19h06 +00:00 A flaw was found in GLib. GVariant deserialization fails to validate that the input conforms to the expected format, leading to denial of service.
7.5
High
CVE-2023-32665 2023-09-14 19h03 +00:00 A flaw was found in GLib. GVariant deserialization is vulnerable to an exponential blowup issue where a crafted GVariant can cause excessive processing, leading to denial of service.
5.5
Medium
CVE-2021-28153 2021-03-11 20h04 +00:00 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.)
5.3
Medium