Empty-file creation via dangling-symlink replacement
Published Mar 11, 2021 · Updated Aug 3, 2024
Improper link resolution in GNOME GLib before 2.66.8 allows attackers to create an empty file through an attacker-controlled dangling symlink. When g_file_replace() receives G_FILE_CREATE_REPLACE_DESTINATION, it follows a dangling link and creates its nonexistent target instead of replacing only the link path. The caller must use that flag on an attacker-controlled dangling symlink; an existing target remains unchanged, limiting the direct consequence to creation of an empty file at an absent target.
Summary
What happened
Improper link resolution in GNOME GLib before 2.66.8 allows attackers to create an empty file through an attacker-controlled dangling symlink. When g_file_replace() receives G_FILE_CREATE_REPLACE_DESTINATION, it follows a dangling link and creates its nonexistent target instead of replacing only the link path. The caller must use that flag on an attacker-controlled dangling symlink; an existing target remains unchanged, limiting the direct consequence to creation of an empty file at an absent target.
The record
- CVE
- CVE-2021-28153
- Published
- Mar 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, CAPEC-132, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream dangling-symlink proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo