CVE-2021-28153

Published: 11 March 2021

An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)

Priority

Medium

CVSS 3 base score: 5.3

Status

Package Release Status
glib2.0
Launchpad, Ubuntu, Debian
Upstream
Released (2.67.6)
Ubuntu 21.04 (Hirsute Hippo) Not vulnerable
(2.68.0-1)
Ubuntu 20.04 LTS (Focal Fossa)
Released (2.64.6-1~ubuntu20.04.3)
Ubuntu 18.04 LTS (Bionic Beaver)
Released (2.56.4-0ubuntu0.18.04.8)
Ubuntu 16.04 ESM (Xenial Xerus)
Released (2.48.2-0ubuntu4.8)
Ubuntu 14.04 ESM (Trusty Tahr) Needs triage

Patches:
Upstream: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1981 (master)
Upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/c80528f17ba25ea7d7089946926b93a98bd1479e (master)
Upstream: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1982 (2.66)
Upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/01c5468e10707cbf78e6e83bbcf1ce9c866f2885 (2.66)