> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/ssti/ssti-information-disclosure-via-python-user-objects.md).

# SSTI Information Disclosure via Python User Objects

SSTI Information Disclosure via Python User Objects notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### Server-side Template Injection with Information Disclosure via User-supplied Objects

The goal of the lab is to use an SSTI caused by the way an object has passed to the template to retrieve sensitive data, especially the secret key of the framework. / We have an account: `content-manager: C0nt3ntM4n4g3r`.

#### Analysis and Identification of ITST

The first step is to cause an error in the template engine with the following expression:

```
{{}}
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5fb46285e64e6b1928b076f16f87fc9573598c4d%2Fimage%20(297).png?alt=media" alt=""><figcaption></figcaption></figure>

* This confirms that we can inject server-side template code.

Then try to display more debugging information by injecting:/ `{% debug %}`

```python
{% debug %}
```

* However, no interesting or sensitive information appears in the output.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4d6a2aed38c8c0833a8808001e44ce77b4c8bc89%2Fimage%20(298).png?alt=media" alt=""><figcaption></figcaption></figure>

#### Recovery of Secret Key

* Since the object passed to the template gives access to the configuration, one tries to read directly the secret key of the framework via the parameters: / `{{settings.SECRET_KEY}}`

```python
{{settings.SECRET_KEY}}
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8378193f896630d9508c393cf47e7dcfe42876b3%2Fimage%20(299).png?alt=media" alt=""><figcaption></figcaption></figure>

* This expression reveals the **secret key** used by the framework.

This value is then submitted to the lab for validation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/web/ssti/ssti-information-disclosure-via-python-user-objects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
