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.)
References
Link | Resource |
---|---|
https://gitlab.gnome.org/GNOME/glib/-/issues/2325 | Exploit Issue Tracking Patch Vendor Advisory |
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6RXTD5HCP2K4AAUSWWZTBKQNHRCTAEOF/ | Mailing List Third Party Advisory |
https://security.netapp.com/advisory/ntap-20210416-0003/ | Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ICUTQPHZNZWX2DZR46QFLQZRHVMHIILJ/ | Mailing List Third Party Advisory |
https://security.gentoo.org/glsa/202107-13 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2022/06/msg00006.html | Mailing List Third Party Advisory |
Information
Published : 2021-03-11 14:15
Updated : 2023-02-03 07:02
NVD link : CVE-2021-28153
Mitre link : CVE-2021-28153
JSON object : View
CWE
CWE-59
Improper Link Resolution Before File Access ('Link Following')
Products Affected
debian
- debian_linux
broadcom
- brocade_fabric_operating_system_firmware
gnome
- glib
fedoraproject
- fedora