# CVE-2023-30771: Apache IoTDB Workbench: apache/iotdb-web-workbench: forge the JWTToken to access workbench

> Attackers can forge JWT tokens to bypass authentication and access the Apache IoTDB web console, requiring the optional workbench component to be enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-787r-6wxc-cg5f, PYSEC-2023-8

## What is CVE-2023-30771?

CVE-2023-30771 is a critical authentication bypass vulnerability in Apache IoTDB Workbench, published on 17 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Authorization vulnerability in Apache Software Foundation Apache IoTDB.This issue affects the iotdb-web-workbench component on 0.13.3. iotdb-web-workbench is an optional component of IoTDB, providing a web console of the database.

This problem is fixed from version 0.13.4 of iotdb-web-workbench onwards.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-30771?

1 open source package ship an affected version, including apache-iotdb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-iotdb` | PyPI | All versions | None |

Products: Apache Iotdb Web Workbench.

## How do I fix CVE-2023-30771?

No fix has been published for CVE-2023-30771 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-30771 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30771 and fix it if it is affected.

What it is: CVE-2023-30771 is a critical authentication bypass vulnerability in Apache IoTDB Workbench, published on 17 Apr 2023. 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-2023-30771 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-iotdb (PyPI): affected all versions; no fix listed

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-2023-30771/ (Markdown: https://insights.sbomify.com/CVE-2023-30771/index.md)
```

## Sources

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

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