CVE-2020-35457

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

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

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

GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib'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.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.(CVE-2021-27218)

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.(CVE-2021-27219)

** DISPUTED ** 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.(CVE-2020-35457)

• CVE-2020-35457: fix integer overflow in g_option_group_add_entries to prevent potential out-of-bounds write
• Bug775510: avoid calling Standard C string/array functions with NULL arguments

• CVE-2020-35457: fix integer overflow in g_option_group_add_entries to prevent potential out-of-bounds write
• Bug775510: avoid calling Standard C string/array functions with NULL arguments

• SECURITY UPDATE: Integer Overflow in g_option_group_add_entries
  • debian/patches/CVE-2020-35457.patch: goption: add a precondition to avoid GOptionEntry list overflow
  • CVE-2020-35457

• CVE-2020-35457: add a precondition in g_option_group_add_entries() to avoid a GOptionEntry list size overflow (GMAXSIZE). Patch backported from amazon-linux-2els.

• CVE-2020-35457: add a precondition in g_option_group_add_entries() to avoid a GOptionEntry list size overflow (GMAXSIZE). Patch backported from amazon-linux-2els.