# CVE-2019-13012: Misconfiguration in n/a > The GNOME GLib keyfile backend creates files and directories with overly permissive permissions, allowing local attackers to read or modify sensitive data. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Jun 2019 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-13012, DLA-1866-2, GHSA-4cmr-h54h-4w78, JLSEC-2025-154, SUSE-SU-2019:1824-1, SUSE-SU-2019:1830-1, SUSE-SU-2019:1830-2, SUSE-SU-2019:1833-1, UBUNTU-CVE-2019-13012, USN-4049-1, USN-4049-2, openSUSE-SU-2019:1749-1 ## What is CVE-2019-13012? CVE-2019-13012 is a high-severity vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource) ## Which versions are affected by CVE-2019-13012? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glib2` | SUSE:Enterprise Storage 4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Enterprise Storage 5 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Enterprise Storage 5 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:HPE Helion OpenStack 8 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.54.3-4.18.1 | | `glib2` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 2.54.3-4.18.1 | | `glib2` | SUSE:Linux Enterprise Module for Package Hub 15 | All versions | 2.54.3-4.18.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 2.38.2-7.12.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 2.38.2-7.12.1 | | `glib2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2.38.2-7.12.1 | | `glib2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:OpenStack Cloud 7 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:OpenStack Cloud 8 | All versions | 2.48.2-12.15.1 | | `glib2` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 2.48.2-12.15.1 | | `glib2` | openSUSE:Leap 15.0 | All versions | 2.54.3-lp150.3.13.1 | Products: Gnome Glib. ## How do I fix CVE-2019-13012? Upgrade to a fixed version. ## Is CVE-2019-13012 being exploited? There is no known exploitation of CVE-2019-13012 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2020-35457](https://insights.sbomify.com/CVE-2020-35457/): Integer overflow in n/a (high 7.8) - [CVE-2009-3289](https://insights.sbomify.com/CVE-2009-3289/): Privilege escalation in n/a (high 7.8) - [CVE-2025-13601](https://insights.sbomify.com/CVE-2025-13601/): Glib: integer overflow in in g_escape_uri_string() (high 7.7) - [CVE-2026-58016](https://insights.sbomify.com/CVE-2026-58016/): Glib: integer underflow in gio/gdbusintrospection.c via "g_dbus_node_info_new_for_xml" (high 7.5) - [CVE-2025-4056](https://insights.sbomify.com/CVE-2025-4056/): Glib: glib crash after long command line (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-13012 and fix it if it is affected. What it is: CVE-2019-13012 is a high-severity vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-13012 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-13012/ (Markdown: https://insights.sbomify.com/CVE-2019-13012/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13012 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13012 - OSV: https://osv.dev/vulnerability/CVE-2019-13012 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-13012/ Summaries are generated and may contain mistakes; the official description above is the record.