Exploiting Template Injection Vulnerabilities
Overview
Cybersecurity skill for exploiting template injection vulnerabilities. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"exploiting template injection vulnerabilities"
"Detecting and exploiting Server-Side Template Injection (SSTI) vulnerabilities a"
During authorized penetration tests when user input is rendered through a server-side template engine
When testing error pages, email templates, PDF generators, or report builders that include user-supplied data
For assessing applications that allow users to customize templates or notification messages
When identifying potential SSTI in parameters that reflect arithmetic results (e.g., {{7*7}} returns 49)
During security assessments of CMS platforms, marketing tools, or any application with templating functionality
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Authorization: Written penetration testing agreement with RCE testing scope
- Burp Suite Professional: For intercepting and modifying template parameters
- tplmap: Automated SSTI exploitation tool (
git clone https://github.com/epinna/tplmap.git)
- SSTImap: Modern SSTI scanner (
pip install sstimap)
- curl: For manual SSTI payload testing
- Knowledge of template engines: Jinja2, Twig, Freemarker, Velocity, Mako, Pebble, ERB, Smarty
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Reconnaissance — Gather information about the target related to template injection vulnerabilities. Identify attack surface.
- Vulnerability Identification — Enumerate potential template injection vulnerabilities weaknesses using automated and manual techniques.
- Exploit Development/Selection — Choose or develop exploits targeting identified template injection vulnerabilities vulnerabilities.
- Execution — Execute the template injection vulnerabilities test in a controlled manner with proper authorization.
- Post-Exploitation — Document the impact and extent of successful exploitation.
- Reporting — Write detailed findings with reproduction steps, impact assessment, and remediation guidance.
Tools
- Vulnerability Scanner — Automated weakness identification
- Exploitation Framework — Controlled exploitation testing
- Reporting Tool — Findings documentation and tracking
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: exploiting-template-injection-vulnerabilities3description: Use when detecting and exploiting Server-Side Template Injection (SSTI) vulnerabilities across Jinja2, Twig, Freemarker, and other template engines to achieve remote code execution. Use when working with exploiting template injection vulnerabilities.4license: Apache-2.05---67# Exploiting Template Injection Vulnerabilities89## Overview1011Cybersecurity skill for exploiting template injection vulnerabilities. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "exploiting template injection vulnerabilities"16- "Detecting and exploiting Server-Side Template Injection (SSTI) vulnerabilities a"171819- During authorized penetration tests when user input is rendered through a server-side template engine20- When testing error pages, email templates, PDF generators, or report builders that include user-supplied data21- For assessing applications that allow users to customize templates or notification messages22- When identifying potential SSTI in parameters that reflect arithmetic results (e.g., `{{7*7}}` returns `49`)23- During security assessments of CMS platforms, marketing tools, or any application with templating functionality242526## When NOT to Use2728- When you lack proper authorization for testing29- For production systems without change management30- When the task requires legal or compliance expertise beyond technical scope313233## Prerequisites3435- **Authorization**: Written penetration testing agreement with RCE testing scope36- **Burp Suite Professional**: For intercepting and modifying template parameters37- **tplmap**: Automated SSTI exploitation tool (`git clone https://github.com/epinna/tplmap.git`)38- **SSTImap**: Modern SSTI scanner (`pip install sstimap`)39- **curl**: For manual SSTI payload testing40- **Knowledge of template engines**: Jinja2, Twig, Freemarker, Velocity, Mako, Pebble, ERB, Smarty4142## Workflow4344```python45# Example: IOC detection46import re4748IOC_PATTERNS = {49 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",50 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",51 "hash_md5": r"\b[a-f0-9]{32}\b",52 "hash_sha256": r"\b[a-f0-9]{64}\b",53}5455def extract_iocs(text: str) -> dict:56 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}57```58591. **Reconnaissance** — Gather information about the target related to template injection vulnerabilities. Identify attack surface.602. **Vulnerability Identification** — Enumerate potential template injection vulnerabilities weaknesses using automated and manual techniques.613. **Exploit Development/Selection** — Choose or develop exploits targeting identified template injection vulnerabilities vulnerabilities.624. **Execution** — Execute the template injection vulnerabilities test in a controlled manner with proper authorization.635. **Post-Exploitation** — Document the impact and extent of successful exploitation.646. **Reporting** — Write detailed findings with reproduction steps, impact assessment, and remediation guidance.6566## Tools6768- **Vulnerability Scanner** — Automated weakness identification69- **Exploitation Framework** — Controlled exploitation testing70- **Reporting Tool** — Findings documentation and tracking717273## Process74751. **Reconnaissance** — Gather target information, identify attack surface, enumerate services761. **Analysis/Exploitation** — Execute the technique, analyze results, document findings771. **Reporting** — Document IOCs, write findings, provide remediation recommendations7879## Verification8081- [ ] All template injection vulnerabilities procedures executed completely and documented82- [ ] Findings validated against multiple data sources83- [ ] False positives identified and filtered84- [ ] Results documented with evidence and timestamps85- [ ] Recommendations provided with risk-based prioritization8687## Anti-Rationalization Table8889| Rationalization | Reality |90|---|---|91| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |92| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |93| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |