> 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/command-injection/blind-command-injection-with-time-delay.md).
# Blind Command Injection with Time Delay
Blind Command Injection with Time Delay notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Blind OS Command Injection with Output Redirection
This lab presents a vulnerability to injection of system commands into feedback functionality. / The application executes a shell command built from the data provided by the user. The output of this command \*\* does not appear in the HTTP response\*\*, which makes it a blind injection. / The objective is to exploit this flaw to cause a 10-second delay\*\*.
#### **Analysis of the Form**
The Submit feedback page sends the following data:
{% code overflow="wrap" %}
```bash
csrf=3dBtfZovWVNJXDv2aXCkmfAOSH9tQt7h&name=hello&email=hello%40gmail.com&subject=hello&message=hello1234
```
{% endcode %}
Since several fields are transmitted, the injection consists of \*\* adding a semicolon before and after the command\*\*, so that it is interpreted separately by the shell.
Example payload to generate a delay:
```bash
;sleep 10;
```
#### **Champ Injectable**
The **email** field reacts to the injection: the answer actually takes **10 seconds**, proof that the command is executed.
Example of modified request:
{% code overflow="wrap" %}
```bash
csrf=3dBtfZovWVNJXDv2aXCkmfAOSH9tQt7h&name=hello&email=hello%40gmail.com;sleep 10 ;&subject=hello&message=hello1234
```
{% endcode %}
---
# 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/command-injection/blind-command-injection-with-time-delay.md?ask=&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.
.png?alt=media)