T1574.009 Path Interception by Unquoted Path

Unter-TechnikEnterprise

Adversaries may execute their own malicious payloads by hijacking vulnerable file path references. Adversaries can take advantage of paths that lack surrounding quotations by placing an executable in a higher level directory within the path, so that Windows will choose the adversary's executable to launch. Service paths and shortcut paths may also be vulnerable to path interception if the path has one or more spaces and is not surrounded by quotation marks (e.g., <code>C:\unsafe path with space\program.exe</code> vs. <code>"C:\safe path with space\program.exe"</code>). (stored in Windows Registry keys) An adversary can place an executable in a higher level directory of the path, and Windows will resolve that executable instead of the intended executable. For example, if the path in a shortcut is <code>C:\program files\myapp.exe</code>, an adversary may create a program at <code>C:\program.exe</code> that will be run instead of the intended program. This technique can be used for persistence if executables are called on a regular basis, as well as privilege escalation if intercepted executables are started by a higher privileged process.

01

Plattformen

Plattformen, für die dies gilt.

Windows
02

Taktiken

ATT&CK-Taktiken, denen diese Technik dient.

03

Unter-Technik von

Die übergeordnete Entität.

04

Gegenmaßnahmen

ATT&CK-Gegenmaßnahmen, die dies verringern.

07

NIST CSF 2.0 — Relevanzbereiche (Protect / Detect)

NIST-CSF-2.0-Bereiche mit dem größten Bezug (belegbasiert).

Abgeleitet aus MITRE CTID (Apache-2.0) und dem NIST-800-53-↔-CSF-Crosswalk (gemeinfrei). Eine indikative Relevanz entlang der Protect-/Detect-Achse — keine Compliance-Bewertung und keine Abdeckungsaussage.

09

Angriffsmuster (1)

CAPEC-Angriffsmuster, die dies ausnutzen.

10

Software (2)

Zugehörige Malware und Tools.

11

Quelle

Wo diese Definition veröffentlicht ist.