> 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/hacking-tools/exploitation/searchsploit.md). # Searchsploit Notas de uso de Searchsploit para consultar Exploit-DB localmente, encontrar exploits públicos y revisar código de prueba de concepto. {% hint style="info" %} **Searchsploit** es una herramienta para buscar rápidamente exploits conocidos y archivos relacionados con vulnerabilidades en la **Exploit-DB** base de datos. Se utiliza en la línea de comandos y funciona sin conexión, lo que la convierte en una herramienta útil para pentesters que quieren identificar exploits en sistemas vulnerables. {% endhint %} {% embed url="" %} #### **Búsqueda básica** Puedes añadir tantos términos de búsqueda como quieras. En la imagen de abajo, estamos buscando exploits que contengan los términos "oracle" y "windows". ```bash searchsploit windows oracle ```

#### **Copiar el exploit al portapapeles y al directorio:** Si quieres copiar el exploit al portapapeles, usa "-p". Por ejemplo: "searchsploit -p XYZ", donde XYZ es el ID del exploit. Si quieres copiar el exploit a tu directorio de trabajo actual, usa "-m". Por ejemplo: "searchsploit -m XYZ", donde XYZ es el ID del exploit ``` searchsploit -m 44553 ```

#### **Examinar un exploit** Si quieres examinar o estudiar un exploit, usa "--examine". Por ejemplo: "searchsploit XYZ --examine", donde XYZ es el ID del exploit. ```bash searchsploit 44553 -examine ```

--- # 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/hacking-tools/exploitation/searchsploit.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.