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.)
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
|Base Score:||5.3||Base Metrics:||AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N|
|Access Vector:||Network||Attack Complexity:||Low|
|Privileges Required:||None||User Interaction:||None|
|Integrity Impact:||Low||Availability Impact:||None|
|Oracle Linux version 8 (glib2)||ELSA-2021-4385||2021-11-16|
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team