> 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/pt-br/ports-and-services/influxdb-8086.md).

# InfluxDB - 8086

Bypass de autenticação da CVE-2019-20933 do InfluxDB, enumeração de banco de dados e descoberta de credenciais.

A porta 8086 expõe a versão 1.7.5 do InfluxDB. O alvo é afetado por um problema de bypass de autenticação no InfluxDB:

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-df2c3205b031cebdc203a734cb931590c0feb7fa%2F%7B317A43DB-B062-4926-AC09-41A23065BA7F%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**Vulnerabilidade:**[CVE-2019-20933](https://nvd.nist.gov/vuln/detail/CVE-2019-20933)

{% embed url="<https://github.com/LorenzoTullini/InfluxDB-Exploit-CVE-2019-20933>" %}

{% hint style="info" %}
Essa vulnerabilidade permite contornar a autenticação explorando um token JWT cujo `SharedSecret` está vazio, o que concede acesso ao banco de dados.
{% endhint %}

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b81693707d06c94521bfa22732490b7d594c2bb2%2F%7B6EE18961-54B1-4819-A38C-D1338A4D6626%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Acesso ao Banco de Dados

Uma vez conectado ao InfluxDB, liste os bancos de dados disponíveis:

```sql
SHOW DATABASES;
```

Selecione o `devzat` banco de dados e explore os dados do usuário. Comece listando as medições (tabelas):

```sql
SHOW MEASUREMENTS;
```

O **`usuário`** tabela contém informações úteis. Para explorar as colunas dessa medição, execute:

```sql
SHOW FIELD KEYS FROM "user";
```

Exiba os primeiros 10 resultados do `usuário` tabela:

```sql
SELECT * FROM "user" LIMIT 10;
```

<table data-header-hidden><thead><tr><th width="357"></th><th></th></tr></thead><tbody><tr><td><strong>senha</strong></td><td><strong>nome de usuário</strong></td></tr><tr><td>WillyWonka2021</td><td>wilhelm</td></tr><tr><td>woBeeYareedahc7Oogeephies7Aiseci</td><td>catherine</td></tr><tr><td>RoyalQueenBee$</td><td>charles</td></tr></tbody></table>

A senha para *catherine* é **`woBeeYareedahc7Oogeephies7Aiseci`**, que permite acesso ao usuário **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/pt-br/ports-and-services/influxdb-8086.md?ask=<question>&goal=<user_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.
