> 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/basic-os-command-injection.md).
# Basic OS Command Injection
Basic OS Command Injection notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### OS Command Injection
This lab presents a vulnerability to injection of system commands into a product's stock verification tool. / The application executes a shell command that includes the product and store credentials provided by the user, then directly returns the raw output of this command in the response.
The goal of the lab is to execute the **whoami** command to identify the current user name.
We find that, under Linux, when you enter a command like:
```bash
pwd
```
it is possible to chain multiple commands using a semicolon:
```bash
pwd;whoami
```
In this case, two parameters are transmitted.
If one inserts a **;** into one or the other, one can execute an arbitrary command because the backend uses a function of the type **system**.
Example:
```bash
productId=1&storeId=1;ls -l
```
---
# 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/basic-os-command-injection.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)
.png?alt=media)
.png?alt=media)