CWE-1386Insecure Operation on Windows Junction / Mount Point

Description

The product opens a file or directory, but it does not properly prevent the name from being associated with a junction or mount point to a destination that is outside of the intended control sphere.

[object Object]

Common consequences

• 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 f

Potential mitigations

• 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

Related CWEs

Recent CVEs classified under this CWE