背景の詳細
導入モード
Implementation : The developer might not consider that when a program in Windows operates with different permissions than the executing user, the use of links, mount points, and junctions might cause the program to access files or directories that are outside of the intended storage location.
適用可能なプラットフォーム
言語
クラス: Not Language-Specific (Undetermined)
オペレーティングシステム
クラス: Windows (Undetermined)
一般的な結果
| スコープ |
影響 |
可能性 |
| Confidentiality | Read Files or Directories
注記:Read arbitrary files by replacing a user-controlled folder with a mount point and additional hard links. | |
| Integrity | Modify Files or Directories
注記:Modify an arbitrary file by replacing the rollback files in installer directories, as they can have the installer execute those rollbacks. | |
| Availability | Modify Files or Directories
注記:Even if there is no control of contents, an arbitrary file delete or overwrite (when running as SYSTEM or admin) can be used for a permanent system denial-of-service, e.g. by deleting a startup configuration file that prevents the service from starting. | |
観察された例
| 参考文献 |
説明 |
| Privileged service allows attackers to delete unauthorized files using a directory junction, leading to arbitrary code execution as SYSTEM. |
| By creating a mount point and hard links, an attacker can abuse a service to allow users arbitrary file read permissions. |
| Chain: race condition (CWE-362) in anti-malware product allows deletion of files by creating a junction (CWE-1386) and using hard links during the time window in which a temporary file is created and deleted. |
| Escape from sandbox for document reader by using a mountpoint [REF-1264] |
潜在的な緩和策
Phases : Architecture and Design
When designing software that will have different rights than the executer, the software should check that files that it is interacting with are not improper hard links or mount points. One way to do this in Windows is to use the functionality embedded in the following command: "dir /al /s /b" or, in PowerShell, use LinkType as a filter. In addition, some software uses authentication via signing to ensure that the file is the correct one to use. Make checks atomic with the file action, otherwise a TOCTOU weakness (CWE-367) can be introduced.
脆弱性マッピングノート
理由 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
コメント : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
ノート
Symbolic links, hard links, junctions, and mount points can be confusing terminology, as there are differences in how they operate between UNIX-based systems and Windows, and there are interactions between them.
This entry is still under development and will continue to see updates and content improvements.
参考文献
REF-1262
Follow the Link: Exploiting Symbolic Links with Ease
Eran Shimony.
https://www.cyberark.com/resources/threat-research-blog/follow-the-link-exploiting-symbolic-links-with-ease REF-1264
Windows 10^H^H Symbolic Link Mitigations
James Forshaw.
https://googleprojectzero.blogspot.com/2015/08/windows-10hh-symbolic-link-mitigations.html REF-1265
Symbolic testing tools
https://github.com/googleprojectzero/symboliclink-testing-tools REF-1266
Understanding and Exploiting Symbolic links in Windows - Symlink Attack EOP
Shubham Dubey.
https://nixhacker.com/understanding-and-exploiting-symbolic-link-in-windows/ REF-1267
Abusing Arbitrary File Deletes to Escalate Privilege and Other Great Tricks
Simon Zuckerbraun.
https://www.zerodayinitiative.com/blog/2022/3/16/abusing-arbitrary-file-deletes-to-escalate-privilege-and-other-great-tricks REF-1271
Abusing privileged file operations
Clément Lavoillotte.
https://troopers.de/troopers19/agenda/7af9hw/
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
Version |
| CWE Content Team |
MITRE |
2022-06-07 +00:00 |
2022-06-28 +00:00 |
4.8 |
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Description, Potential_Mitigations |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Description, References |