p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in glib2.0 · Seite 2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für glib2.0: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 33

  1. CVE-2024-34397

    Mittel · CVSS 5.2EPSS 0,76%Keine Korrektur veröffentlicht

    CVE-2024-34397

    An issue was discovered in GNOME GLib before 2.78.5, and 2.79.x and 2.80.x before 2.80.1. When a GDBus-based client subscribes to signals from a trusted system service such as NetworkManager on a shared computer, other users of the same computer can send spoofed D-Bus signals that the GDBus-based client will wrongly interpret as having been sent by the trusted system service. This could lead to the GDBus-based client behaving incorrectly, with an application-dependent impact.

    Veröffentlicht Aktualisiert
  2. CVE-2023-32636

    Mittel · CVSS 4.7EPSS 0,79%Korrektur verfügbar

    CVE-2023-32636

    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.

    • Auf 2.40.2-0ubuntu1.1+esm6 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2023-32643

    Mittel · CVSS 5.3EPSS 0,38%Korrektur verfügbar

    CVE-2023-32643

    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.

    • Auf 2.40.2-0ubuntu1.1+esm6 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2023-32665

    Mittel · CVSS 5.5EPSS 0,39%Korrektur verfügbar

    Gvariant deserialisation does not match spec for non-normal data

    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.

    • Auf 2.40.2-0ubuntu1.1+esm6 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2021-28153

    Mittel · CVSS 5.3EPSS 2,71%Keine Korrektur veröffentlicht

    CVE-2021-28153

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

    Veröffentlicht Aktualisiert
  6. CVE-2019-13012

    Hoch · CVSS 7.5EPSS 3,21%Korrektur verfügbar

    CVE-2019-13012

    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.

    • Auf 2.40.2-0ubuntu1.1+esm3 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2012-0039

    Hoch · CVSS 7.5EPSS 2,04%Keine Korrektur veröffentlicht

    CVE-2012-0039

    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.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →