Incorrect Permission Assignment for Critical Resource The advisory has been revoked - it doesn't affect any version of package gio-branding-upstream  (opens in a new tab)


Threat Intelligence

EPSS
3.21% (88th 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-SLES150-GIOBRANDINGUPSTREAM-2743897
  • published14 Apr 2022
  • disclosed12 Jul 2019

Introduced: 12 Jul 2019

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

Amendment

The SLES security team deemed this advisory irrelevant for SLES:15.0.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gio-branding-upstream package and not the gio-branding-upstream package as distributed by SLES.

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.