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.)
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2021-03-11T21:04:15
Updated: 2024-08-03T21:40:12.088Z
Reserved: 2021-03-11T00:00:00
Link: CVE-2021-28153
Vulnrichment
No data.
NVD
Status : Modified
Published: 2021-03-11T22:15:12.777
Modified: 2024-11-21T05:59:11.820
Link: CVE-2021-28153
Redhat