Vulnerability in glib2.0
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-13012 has been found in glib2.0.
Data can be tampered with by attackers.
What to do: upgrade glib2.0 to 2.60.5-1 or later.
If unsure, ask your IT team or search "glib2.0 DEBIAN-CVE-2019-13012" on the vendor's site.
DEBIAN-CVE-2019-13012 (glib2.0)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.60.5-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in glib2.0.
Check the vendor advisory for the affected versions of glib2.0.
Severity: ?. Data can be tampered with by attackers.
Update to 2.60.5-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'glib2.0' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'glib2.0' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
glib2.0を grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade glib2.0 to 2.60.5-1ステージング環境で 2.60.5-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | glib2.0 |
< 2.60.5-1 |
2.60.5-1 |
| Debian:13 | glib2.0 |
< 2.60.5-1 |
2.60.5-1 |
| Debian:14 | glib2.0 |
< 2.60.5-1 |
2.60.5-1 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org