> 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/es/web/command-injection.md).
# Inyección de comandos del SO
Inyección de comandos del sistema operativo, inyección ciega de comandos, retrasos temporales, redirección de salida, detección OOB y exfiltración de comandos.
Notas sobre inyección de comandos para los laboratorios de PortSwigger Web Security Academy, centradas en pasos de prueba prácticos, validación con Burp Suite, comportamiento de cargas útiles y flujo de trabajo de explotación.
## Flujo de trabajo de pruebas
1. Identifica la funcionalidad vulnerable y la solicitud, parámetro, encabezado, cookie o sink del lado del navegador relevantes.
2. Reproduce el comportamiento en Burp Suite con una carga útil mínima antes de escalar el ataque.
3. Valida el impacto con una prueba de concepto clara, como acceso a la cuenta, divulgación de datos, ejecución de código, SSRF o cambio de estado.
4. Mantén sin cambios las cargas útiles, las URL, los tokens y las credenciales del laboratorio mientras documentas la ruta de explotación.
## Laboratorios
---
# 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/es/web/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.