Incorrect Permission Assignment for Critical Resource Affecting glib2.0 package, versions <2.42.1-1+deb8u3


0.0
high

Snyk CVSS

    Attack Complexity Low
    Integrity High

    Threat Intelligence

    EPSS 0.43% (75th percentile)
Expand this section
NVD
7.5 high
Expand this section
SUSE
8.1 high
Expand this section
Red Hat
4.4 medium

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-DEBIAN8-GLIB20-451224
  • published 28 Jun 2019
  • disclosed 28 Jun 2019

How to fix?

Upgrade Debian:8 glib2.0 to version 2.42.1-1+deb8u3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:8 relevant fixed versions and status.

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.