CVE-2021-28153Link Following in Glib

CWE-59Link Following8 documents8 sources
Severity
5.3MEDIUMNVD
EPSS
0.7%
top 27.33%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedMar 11
Latest updateMay 24

Description

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.)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitability: 3.9 | Impact: 1.4

Affected Packages1 packages

NVDgnome/glib< 2.66.8

Also affects: Debian Linux 9.0, Fedora 33

Patches

🔴Vulnerability Details

3
GHSA
GHSA-9hh6-p5c5-mmmf: An issue was discovered in GNOME GLib before 22022-05-24
CVEList
CVE-2021-28153: An issue was discovered in GNOME GLib before 22021-03-11
OSV
CVE-2021-28153: An issue was discovered in GNOME GLib before 22021-03-11

📋Vendor Advisories

4
Ubuntu
GLib vulnerability2021-03-15
Red Hat
glib: g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION creates empty target for dangling symlink2021-03-10
Microsoft
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 t2021-03-09
Debian
CVE-2021-28153: glib2.0 - An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is us...2021