> 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/ports-and-services/influxdb-8086.md).
# InfluxDB - 8086
Bypass de autenticación de InfluxDB CVE-2019-20933, enumeración de base de datos y descubrimiento de credenciales.
El puerto 8086 expone la versión 1.7.5 de InfluxDB. El objetivo se ve afectado por un problema de omisión de autenticación en InfluxDB:
**Vulnerabilidad:**[CVE-2019-20933](https://nvd.nist.gov/vuln/detail/CVE-2019-20933)
{% embed url="" %}
{% hint style="info" %}
Esta vulnerabilidad permite omitir la autenticación explotando un token JWT cuyo `SharedSecret` está vacío, lo que concede acceso a la base de datos.
{% endhint %}
#### Acceso a la base de datos
Una vez conectado a InfluxDB, enumera las bases de datos disponibles:
```sql
SHOW DATABASES;
```
Selecciona la `devzat` base de datos y explora los datos de usuario. Empieza por listar las mediciones (tablas):
```sql
SHOW MEASUREMENTS;
```
El **`usuario`** la tabla contiene información útil. Para explorar las columnas de esta medición, ejecuta:
```sql
SHOW FIELD KEYS FROM "user";
```
Muestra los primeros 10 resultados de la `usuario` tabla:
```sql
SELECT * FROM "user" LIMIT 10;
```
contraseña
nombre de usuario
WillyWonka2021
wilhelm
woBeeYareedahc7Oogeephies7Aiseci
catherine
RoyalQueenBee$
charles
La contraseña de *catherine* es **`woBeeYareedahc7Oogeephies7Aiseci`**, que permite acceder al usuario **flag**.
---
# 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/ports-and-services/influxdb-8086.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.
