TInjA is a CLI tool for testing web pages for template injection vulnerabilities.
It supports 44 of the most relevant template engines (as of September 2023) for eight different programming languages.
TInjA was developed by Hackmanit and Maximilian Hildebrand.
- Features
- Supported Template Engines
- Installation
- Usage
- Troubleshooting
- TODOs
- Background Information
- License
- Automatic detection of template injection possibilities and identification of the template engine in use.
- 44 of the most relevant template engines supported (see Supported Template Engines).
- Both SSTI and CSTI vulnerabilities are detected.
- SSTI = server-side template injection
- CSTI = client-side template injection
- Efficient scanning thanks to the usage of polyglots:
- On average only five polyglots are sent to the web page until the template injection possibility is detected and the template engine identified.
- Pass crawled URLs to TInjA in JSONL format.
- Pass a raw HTTP request to TInjA.
- Set custom headers, cookies, POST parameters, and query parameters.
- Route the traffic through a proxy (e.g., Burp Suite).
- Configure Ratelimiting.
- DotLiquid
- Fluid
- Razor Engine
- Scriban
- EEx
- html/template
- text/template
- Freemarker
- Groovy
- Thymeleaf
- Velocity
- Angular.js
- Dot
- EJS
- Eta
- Handlebars
- Hogan.js
- Mustache
- Nunjucks
- Pug
- Twig.js
- Underscore
- Velocity.js
- Vue.js
- Blade
- Latte
- Mustache.php
- Smarty
- Twig
- Chameleon
- Cheetah3
- Django
- Jinja2
- Mako
- Pystache
- SimpleTemplate Engine
- Tornado
- ERB
- Erubi
- Erubis
- Haml
- Liquid
- Mustache
- Slim
Prebuilt binaries of TInjA are provided on the releases page.
Requirements: go1.21 or higher
go install -v github.com/Hackmanit/TInjA@latest
- Scan a single URL:
tinja url -u "http://example.com/"
- Scan multiple URLs:
tinja url -u "http://example.com/" -u "http://example.com/path2"
- Scan URLs provided in a file:
tinja url -u "file:/path/to/file"
- Scan a single URL by passing a file with a raw HTTP request:
tinja raw -R "/path/to/file"
- Scan URLs with additional information provided in a JSONL file:
tinja jsonl -j "/path/to/file"
- Each line of the JSONL file must contain a single JSON object. The whole JSON object must be in one line. Each object must have the following structure (extra line breaks and indentation are for display purposes only):
{
"request":{
"method":"POST",
"endpoint":"http://example.com/path",
"body":"name=Kirlia",
"headers":{
"Content-Type":"application/x-www-form-urlencoded"
}
}
--header
/-H
specifies headers which shall be added to the request.- Example:
tinja url -u "http://example.com/" -H "Authentication: Bearer ey..."
- Example:
--cookie
/-c
specifies cookies which shall be added to the request.- Example:
tinja url -u "http://example.com/" -c "PHPSESSID=ABC123..."
- Example:
--data
/-d
specifies the POST body which shall be added to the request.- Example:
tinja url -u "http://example.com/" -d "username=Kirlia&password=notguessable"
- Example:
--csti
enables the scanning for CSTI.- Example:
tinja url -u "http://example.com/" --csti
- Example:
By default TInjA only scans for SSTI. A headless browser is utilized for scanning for CSTI, which may increase RAM and CPU usage.
--reportpath
enables generating a report in JSONL format. The report will be updated after each scanned URL and will be stored at the provided path.- Example:
tinja url -u "http://example.com/" --reportpath "/home/user/Documents"
- Example:
--proxyurl
specifies the URL and port of a proxy to be used for scanning.- Example:
tinja url -u "http://example.com/" --proxyurl "http://127.0.0.1:8080"
- Example:
--proxycertpath
specifies the CA certificate of the proxy in PEM format (needed when scanning HTTPS URLs).- Example
tinja url -u "http://example.com/" --proxyurl "http://127.0.0.1:8080" --proxycertpath "/home/user/Documents/cacert.pem"
- Example
To scan HTTPS URLs using a proxy a CA certificate of the proxy in PEM format is needed. Burp Suite CA certificates are provided in DER format, for example. To convert them, the following command can be used:
openssl x509 -inform DER -outform PEM -text -in cacert.der -out cacert.pem
--ratelimit
/-r
specifies the number of maximum requests per second allowed. By default, this number is unrestricted.- Example:
tinja url -u "http://example.com/" --ratelimit 10
- Example:
[ERR] Couldn't connect to URL: remote error: tls: user canceled
- When using a proxy and connecting via HTTPS, the proxy's CA certificate (.pem) needs to be specified with
--proxycertpath
(see Use a Proxy).
- When using a proxy and connecting via HTTPS, the proxy's CA certificate (.pem) needs to be specified with
[ERR] Error reading response from target server via proxy: malformed HTTP response "HTTP/1.1"
- Disable
Default to HTTP/2 if the server supports it
in Burp Suite's settings (Network
>HTTP
).
- Disable
TINJA
marker to mark where the polyglots shall be placed.- Support for multipart bodies and JSON.
- Optional: Blind SSTI Payloads (e.g., sleep payloads).
- Feedback, whether CSTI or SSTI was detected.
- Check headless browser's console for template engine error messages (see go-rod/rod#330).
- Improve Error Detection, when input is not reflected
A blog post providing more information about template injection and TInjA – the Template INJection Analyzer can be found here:
Template Injection Vulnerabilities – Understand, Detect, Identify
TInjA was developed as a part of a master's thesis by Maximilian Hildebrand. You can find results of the master's thesis publicly available here:
- Template Injection Table
- Template Injection Playground
- TInjA – the Template INJection Analyzer
- Master's Thesis (PDF)
TInjA – the Template INJection Analyzer was developed by Hackmanit and Maximilian Hildebrand as a part of his master's thesis. TInjA – the Template INJection Analyzer is licensed under the Apache License, Version 2.0.