dbcve.org
IotdbApplication · Apache

CVE-2022-38370

HIGH · 7.5 CVSS v3.1 Published 2022-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache IoTDB grafana-connector v0.13.0 contains an unauthenticated API interface that exposes internal database structures due to missing authorization checks. This allows unauthenticated attackers to retrieve sensitive metadata about the database system.

MitigationUpgrade grafana-connector to version 0.13.1 which implements proper authorization controls on the affected interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IotdbApplication
Affected:= 0.13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if grafana-connector is deployed
    Review your IoTDB deployment to determine if the grafana-connector component is installed and running. Check for processes or services named grafana-connector or check the installation directory for grafana-connector files.
    Affected if grafana-connector is present and running in your environment
  2. Check grafana-connector version
    Locate the grafana-connector version file or examine the deployed JAR/war files. Common locations include the grafana-connector lib directory or the IoTDB tools folder. Run: ls -la grafana-connector* or check META-INF/MANIFEST.MF inside the connector JAR.
    Affected if The version is exactly 0.13.0
  3. Verify API endpoint accessibility
    Attempt to access the internal API endpoints without providing credentials. The vulnerable endpoints expose database metadata. Try: curl http://localhost:PORT/internal/ or similar internal paths that the connector exposes.
    Affected if The API returns database metadata (such as storage groups, timeseries, or schema information) without requiring authentication
  4. Check for authorization configuration
    Examine the grafana-connector configuration files (typically in conf/ or config/ directory) for authorization settings. Look for properties related to auth, authorization, or access control on the API endpoints.
    Affected if No authorization mechanism is configured for the exposed API interface

You are affected if grafana-connector version 0.13.0 is deployed and its internal API endpoints are accessible without authentication, exposing database metadata.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade grafana-connector to version 0.13.1 which implements proper authorization controls on the affected interface.

Recommended fix High confidence

0.13.1

  1. Download Apache IoTDB grafana-connector version 0.13.1 from the official Apache IoTDB distribution
  2. Replace the existing grafana-connector 0.13.0 installation with version 0.13.1
  3. Restart the grafana-connector service to apply the updated version
  4. Verify the new version is running and the authorization is properly enforced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iotdb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data