Incorrect Permission Assignment for Critical Resource Affecting glib2.0 package, versions <2.48.2-0ubuntu4.4


Severity

Recommended
medium

Based on Ubuntu security rating.

Threat Intelligence

EPSS
0.57% (78th percentile)

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 IDSNYK-UBUNTU1604-GLIB20-451402
  • published28 Jun 2019
  • disclosed28 Jun 2019

Introduced: 28 Jun 2019

CVE-2019-13012  (opens in a new tab)
CWE-732  (opens in a new tab)

How to fix?

Upgrade Ubuntu:16.04 glib2.0 to version 2.48.2-0ubuntu4.4 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 Ubuntu. See How to fix? for Ubuntu:16.04 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.