Homepage

Incorrect Permission Assignment for Critical Resource Affecting glib2 package, versions <0:2.56.4-9.el8

Severity

 Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.65% (80th 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-RHEL8-GLIB2-4037705
  • published26 Jul 2021
  • disclosed28 Jun 2019
Report a new vulnerability Found a mistake?

Introduced: 28 Jun 2019

CVE-2019-13012  (opens in a new tab)
CWE-732  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade RHEL:8 glib2 to version 0:2.56.4-9.el8 or higher.
This issue was patched in RHSA-2021:1586.

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by RHEL. See How to fix? for RHEL: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.

References