Glib GNOME Glib

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in GNOME Glib.

By the Year

In 2024 there have been 1 vulnerability in GNOME Glib . Last year Glib had 5 security vulnerabilities published. Right now, Glib is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 1 0.00
2023 5 6.76
2022 1 5.50
2021 3 6.77
2020 2 6.85
2019 3 7.93
2018 2 8.65

It may take a day or so for new Glib vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent GNOME Glib Security Vulnerabilities

GNOME GLib 2.x SOCKS4 Proxy Buffer Overflow Vulnerability

CVE-2024-52533 - November 11, 2024

gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient for a trailing '\0' character.

A flaw was found in GLib

CVE-2023-32643 7.8 - High - September 14, 2023

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.

Memory Corruption

A flaw was found in GLib

CVE-2023-32611 5.5 - Medium - September 14, 2023

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.

Resource Exhaustion

A flaw was found in GLib

CVE-2023-32665 5.5 - Medium - September 14, 2023

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.

Marshaling, Unmarshaling

A flaw was found in GLib

CVE-2023-29499 7.5 - High - September 14, 2023

A flaw was found in GLib. GVariant deserialization fails to validate that the input conforms to the expected format, leading to denial of service.

Resource Exhaustion

A flaw was found in glib

CVE-2023-32636 7.5 - High - September 14, 2023

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.

Marshaling, Unmarshaling

A flaw was found in glib before version 2.63.6

CVE-2021-3800 5.5 - Medium - August 23, 2022

A flaw was found in glib before version 2.63.6. Due to random charset alias, pkexec can leak content from files owned by privileged users to unprivileged ones under the right condition.

Information Disclosure

An issue was discovered in GNOME GLib before 2.66.8

CVE-2021-28153 5.3 - Medium - March 11, 2021

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.)

insecure temporary file

An issue was discovered in GNOME GLib before 2.66.7 and 2.67.x before 2.67.4

CVE-2021-27218 7.5 - High - February 15, 2021

An issue was discovered in GNOME GLib before 2.66.7 and 2.67.x before 2.67.4. If g_byte_array_new_take() was called with a buffer of 4GB or more on a 64-bit platform, the length would be truncated modulo 2**32, causing unintended length truncation.

Incorrect Conversion between Numeric Types

An issue was discovered in GNOME GLib before 2.66.6 and 2.67.x before 2.67.3

CVE-2021-27219 7.5 - High - February 15, 2021

An issue was discovered in GNOME GLib before 2.66.6 and 2.67.x before 2.67.3. The function g_bytes_new has an integer overflow on 64-bit platforms due to an implicit cast from 64 bits to 32 bits. The overflow could potentially lead to memory corruption.

Incorrect Conversion between Numeric Types

GNOME GLib before 2.65.3 has an integer overflow, that might lead to an out-of-bounds write, in g_option_group_add_entries

CVE-2020-35457 7.8 - High - December 14, 2020

GNOME GLib before 2.65.3 has an integer overflow, that might lead to an out-of-bounds write, in g_option_group_add_entries. NOTE: the vendor's position is "Realistically this is not a security issue. The standard pattern is for callers to provide a static list of option entries in a fixed number of calls to g_option_group_add_entries()." The researcher states that this pattern is undocumented

Memory Corruption

GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly to a target address instead of connecting via a proxy server when configured to do so

CVE-2020-6750 5.9 - Medium - January 09, 2020

GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly to a target address instead of connecting via a proxy server when configured to do so, because the proxy_addr field is mishandled. This bug is timing-dependent and may occur only sporadically depending on network delays. The greatest security relevance is in use cases where a proxy is used to help with privacy/anonymity, even though there is no technical barrier to a direct connection. NOTE: versions before 2.60 are unaffected.

The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using g_file_make_directory_with_parents (kfsb->dir

CVE-2019-13012 7.5 - High - June 28, 2019

The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using g_file_make_directory_with_parents (kfsb->dir, NULL, NULL) and files using g_file_replace_contents (kfsb->file, contents, length, NULL, FALSE, G_FILE_CREATE_REPLACE_DESTINATION, NULL, NULL, NULL). Consequently, it does not properly restrict directory (and file) permissions. Instead, for directories, 0777 permissions are used; for files, default file permissions are used. This is similar to CVE-2019-12450.

Incorrect Permission Assignment for Critical Resource

file_copy_fallback in gio/gfile.c in GNOME GLib 2.15.0 through 2.61.1 does not properly restrict file permissions while a copy operation is in progress

CVE-2019-12450 9.8 - Critical - May 29, 2019

file_copy_fallback in gio/gfile.c in GNOME GLib 2.15.0 through 2.61.1 does not properly restrict file permissions while a copy operation is in progress. Instead, default permissions are used.

Race Condition

gio/gsocketclient.c in GNOME GLib 2.59.2 does not ensure

CVE-2019-9633 6.5 - Medium - March 08, 2019

gio/gsocketclient.c in GNOME GLib 2.59.2 does not ensure that a parent GTask remains alive during the execution of a connection-attempting enumeration, which allows remote attackers to cause a denial of service (g_socket_client_connected_callback mishandling and application crash) via a crafted web site, as demonstrated by GNOME Web (aka Epiphany).

Improper Input Validation

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c

CVE-2018-16429 7.5 - High - September 04, 2018

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c, related to utf8_str().

Out-of-bounds Read

In GNOME GLib 2.56.1

CVE-2018-16428 9.8 - Critical - September 04, 2018

In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference.

NULL Pointer Dereference

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application

CVE-2012-0039 - January 14, 2012

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

Cryptographic Issues

The g_file_copy function in glib 2.0 sets the permissions of a target file to the permissions of a symbolic link (777), which

CVE-2009-3289 7.8 - High - September 22, 2009

The g_file_copy function in glib 2.0 sets the permissions of a target file to the permissions of a symbolic link (777), which allows user-assisted local users to modify files of other users, as demonstrated by using Nautilus to modify the permissions of the user home directory.

Incorrect Permission Assignment for Critical Resource

Multiple integer overflows in glib/gbase64.c in GLib before 2.20 allow context-dependent attackers to execute arbitrary code via a long string

CVE-2008-4316 - March 14, 2009

Multiple integer overflows in glib/gbase64.c in GLib before 2.20 allow context-dependent attackers to execute arbitrary code via a long string that is converted either (1) from or (2) to a base64 representation.

Numeric Errors

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for GNOME Glib or by GNOME? Click the Watch button to subscribe.

GNOME
Vendor

GNOME Glib
Product

subscribe