# CVE-2022-38370: No authorization of DatabaseConnectController in grafana-connector.

> An unauthenticated attacker can access the DatabaseConnectController interface in Apache IoTDB grafana-connector, exposing internal database structure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c86f-9grv-pmqf

## What is CVE-2022-38370?

CVE-2022-38370 is a high-severity missing authorization vulnerability in Apache IoTDB, published on 5 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache IoTDB grafana-connector version 0.13.0 contains an interface without authorization, which may expose the internal structure of database. Users should upgrade to version 0.13.1 which addresses this issue.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-38370?

2 open source packages ship an affected version, including org.apache.iotdb:iotdb-grafana-connector. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.iotdb:iotdb-grafana-connector` | Maven | All versions | 0.13.1 |
| `org.apache.iotdb:iotdb-grafana-connector` | Maven | All versions | 0.13.1 |

Products: Apache Iotdb.

## How do I fix CVE-2022-38370?

Upgrade org.apache.iotdb:iotdb-grafana-connector to 0.13.1 or later.

## Is CVE-2022-38370 being exploited?

There is no known exploitation of CVE-2022-38370 in the wild and no public exploit code.

## Other vulnerabilities in Apache IoTDB

- [CVE-2026-24014](https://insights.sbomify.com/CVE-2026-24014/): Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write (critical 9.8)
- [CVE-2026-24015](https://insights.sbomify.com/CVE-2026-24015/): Apache IoTDB: Insecure Default Configuration Vulnerability (critical 9.8)
- [CVE-2026-24713](https://insights.sbomify.com/CVE-2026-24713/): Apache IoTDB: JEXL Expression Injection Vulnerability (critical 9.8)
- [CVE-2024-24780](https://insights.sbomify.com/CVE-2024-24780/): Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function (critical 9.8)
- [CVE-2023-46226](https://insights.sbomify.com/CVE-2023-46226/): Apache IoTDB: Remote Code Execution (RCE) risk via the UDF (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38370 and fix it if it is affected.

What it is: CVE-2022-38370 is a high-severity missing authorization vulnerability in Apache IoTDB, published on 5 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38370 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.iotdb:iotdb-grafana-connector (Maven): affected all versions; fixed in 0.13.1
- org.apache.iotdb:iotdb-grafana-connector (Maven): affected all versions; fixed in 0.13.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-38370/ (Markdown: https://insights.sbomify.com/CVE-2022-38370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-38370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-38370
- OSV: https://osv.dev/vulnerability/CVE-2022-38370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-38370/
Summaries are generated and may contain mistakes; the official description above is the record.