CVE-2019-13012 json
The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using...
published 7y ago modified 3mo ago also EUVD-2019-4585 , JLSEC-2025-154
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- julia Glib_jll 2.68.1+0
- gnome glib 2.59.1
- glib2.0 Debian 14, Debian 13, Debian 12 2.60.5-1
debian advisories DEBIAN-CVE-2019-13012
- glib2.0 Ubuntu 16.04 LTS 2.48.2-0ubuntu4.4
- glib2.0 Ubuntu 18.04 LTS 2.56.4-0ubuntu0.18.04.4
- glib2.0 Ubuntu Pro 14.04 LTS 2.40.2-0ubuntu1.1+esm3
ubuntu advisories UBUNTU-CVE-2019-13012
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- gdm RHEL 8 1:3.28.3-39.el8
- glib2 RHEL 8 2.56.4-9.el8
- glib2-fam RHEL 8 2.56.4-9.el8
- glib2-tests RHEL 8 2.56.4-9.el8
- webkit2gtk3 RHEL 8 2.30.4-1.el8
- webkit2gtk3-jsc RHEL 8 2.30.4-1.el8
red hat advisories RHSA-2021:1586
- glib2 SLE Module for Package Hub 15, SLE Module for Basesystem 15 SP1, SLE Module for Basesystem 15 2.54.3-4.18.1
- glib2 SLES 12 SP4, SLES 12 SP3-BCL, SLES 12 SP2-BCL +14 more 2.48.2-12.15.1
- glib2 SLES for SAP 12 SP1, SLES 12-LTSS, SLES 12 SP1-LTSS 2.38.2-7.12.1
suse advisories SUSE-SU-2019:1833-1SUSE-SU-2019:1830-1SUSE-SU-2019:1830-2SUSE-SU-2019:1824-1
- glib2 openSUSE Leap 15.0 2.54.3-lp150.3.13.1
opensuse advisories openSUSE-SU-2019:1749-1
- gjs AlmaLinux 8 1.56.2-5.el8
- gtk2 AlmaLinux 8 2.24.32-5.el8
- gvfs AlmaLinux 8 1.36.2-11.el8
- vala AlmaLinux 8 0.40.19-2.el8
- atkmm AlmaLinux 8 2.24.2-7.el8
- gamin AlmaLinux 8 0.1.10-32.el8
- woff2 AlmaLinux 8 1.0.2-5.el8
- cairomm AlmaLinux 8 1.12.0-8.el8
almalinux advisories ALSA-2021:1586
- gdm Rocky Linux 8 1:3.28.3-39.el8
- gjs Rocky Linux 8 1.56.2-5.el8
- gtk2 Rocky Linux 8 2.24.32-5.el8
- gvfs Rocky Linux 8 1.36.2-11.el8
- vala Rocky Linux 8 0.40.19-2.el8
- atkmm Rocky Linux 8 2.24.2-7.el8
- gamin Rocky Linux 8 0.1.10-32.el8
- woff2 Rocky Linux 8 1.0.2-5.el8
rocky linux advisories RLSA-2021:1586
Is CVE-2019-13012 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-13012 updated cvss 4.4
glib2: insecure permissions for files and directories
-
Red Hat Enterprise Linux 6 glib2affected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 glib2, glib2-fam, glib2-testsaffected: no fix available “Fix deferred”
-
Red Hat CodeReady Linux Builder (v. 8) glib2-doc 2.56.4-9.el8, glib2-static 2.56.4-9.el8, glib2-debuginfo 2.56.4-9.el8, glib2-debugsource 2.56.4-9.el8, glib2-fam-debuginfo 2.56.4-9.el8, glib2-devel-debuginfo 2.56.4-9.el8, +1 more Red Hat Enterprise Linux BaseOS (v. 8) glib2 2.56.4-9.el8, glib2-fam 2.56.4-9.el8, glib2-tests 2.56.4-9.el8fixed: vendor fix RHSA-2021:1586
-
Red Hat CodeReady Linux Builder (v. 8) gvfs 1.36.2-11.el8, vala 0.40.19-2.el8, libsass 3.4.5-6.el8, libdazzle 3.28.5-2.el8, libepubgen 0.1.0-3.el8, nautilus 3.28.1-15.el8 Red Hat Enterprise Linux 5 glib2 Red Hat Enterprise Linux AppStream (v. 8) gjs 1.56.2-5.el8, gdm 3.28.3-39.el8, woff2 1.0.2-5.el8, atkmm 2.24.2-7.el8, gtk2 2.24.32-5.el8, gvfs 1.36.2-11.el8, +73 more Red Hat Enterprise Linux BaseOS (v. 8) gamin 0.1.10-32.el8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.21% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| OSV | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| julia | Glib_jll | <2.68.1+0 |
2.68.1+0 |
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
gitlab.gnome.org
/GNOME/glib/commit/5e4da714f00f6bfb2ccd6d73d61329c6f3a08429
patch, third-party-advisory, web
-
usn.ubuntu.com
/4049-1/
vendor-advisory, web
-
usn.ubuntu.com
/4049-2/
vendor-advisory, web
-
lists.opensuse.org
/opensuse-security-announce/2019-07/msg00022.html
vendor-advisory, web
-
gitlab.gnome.org
/GNOME/glib/issues/1658
third-party-advisory, web
-
gitlab.gnome.org
/GNOME/glib/merge_requests/450
issue-tracking, third-party-advisory, web
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=931234#12
web
-
lists.debian.org
/debian-lts-announce/2019/07/msg00029.html
mailing-list, web
-
lists.debian.org
/debian-lts-announce/2019/08/msg00004.html
mailing-list, web
-
security.netapp.com
/advisory/ntap-20190806-0003/
web
-
lists.apache.org
/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
mailing-list, web
-
lists.apache.org
/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
mailing-list, web
Sources
- CVE List CVE-2019-13012
- NVD CVE-2019-13012
- OSV JLSEC-2025-154
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.