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.)
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3044-1 | glib2.0 security update |
EUVD |
EUVD-2021-14851 | 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.) |
Ubuntu USN |
USN-4764-1 | GLib vulnerability |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-03T21:40:12.088Z
Reserved: 2021-03-11T00:00:00.000Z
Link: CVE-2021-28153
No data.
Status : Modified
Published: 2021-03-11T22:15:12.777
Modified: 2024-11-21T05:59:11.820
Link: CVE-2021-28153
OpenCVE Enrichment
No data.
Weaknesses
Debian DLA
EUVD
Ubuntu USN