VariantIncomplete

CWE-64Windows Shortcut Following (.LNK)

Category: other

Description

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.

Common consequences· 1

  • Confidentiality / Integrity — Read Files or Directories, Modify Files or Directories
    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.

Potential mitigations· 1

  • [Architecture and Design]

References

  1. https://cwe.mitre.org/data/definitions/64.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Link Resolution Before File Access ('Link Following')
CWE
Windows Hard Link
CWE
UNIX Symbolic Link (Symlink) Following
CWE
Insecure Operation on Windows Junction / Mount Point
CWE
Path Traversal: '\..\filename'
CWE
Path Traversal: '\\UNC\share\name\' (Windows UNC Share)
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.