CWE-64: Windows Shortcut Following (.LNK)
The product, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
View on MITREExtended Description
The shortcut (file with the .lnk extension) can permit an attacker to read/write a file that they originally did not have permissions to access.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (7)
network access control service executes program with high privileges and allows symlink to invoke another executable or perform DLL injection.
View DetailsMail client allows remote attackers to bypass the user warning for executable attachments such as .exe, .com, and .bat by using a .lnk file that refers to the attachment, aka "Stealth Attachment."
View DetailsFTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.
View DetailsFTP server allows remote attackers to read arbitrary files and directories by uploading a .lnk (link) file that points to the target file.
View DetailsBrowser allows remote malicious web sites to overwrite arbitrary files by tricking the user into downloading a .LNK (link) file twice, which overwrites the file that was referenced in the first .LNK file.
View DetailsRootkits can bypass file access restrictions to Windows kernel directories using NtCreateSymbolicLinkObject function to create symbolic link
View DetailsCWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-64: Windows Shortcut Following (.LNK)?+
CWE-64: Windows Shortcut Following (.LNK) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. The shortcut (file with the .lnk extension) can permit an attacker to read/write a file that they originally did not have permissions to access.
What are the security consequences of Windows Shortcut Following (.LNK)?+
If exploited, CWE-64 (Windows Shortcut Following (.LNK)) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Files or Directories and Modify Files or Directories.
Which programming languages are affected by Windows Shortcut Following (.LNK)?+
CWE-64 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What are real-world examples of Windows Shortcut Following (.LNK)?+
MITRE documents real CVEs mapped to CWE-64, including CVE-2019-19793, CVE-2000-0342, CVE-2001-1042, CVE-2001-1043 and CVE-2005-0587. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-64 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.