dbcve.org
IotdbApplication · Apache

CVE-2023-24829

HIGH · 8.8 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to 0.13.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Authorization vulnerability in Apache Software Foundation Apache IoTDB.This issue affects the iotdb-web-workbench component from 0.13.0 before 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.3 of iotdb-web-workbench onwards.

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

An incorrect authorization vulnerability exists in the iotdb-web-workbench component (versions 0.13.0 before 0.13.3) of Apache IoTDB database. This web console component fails to properly enforce authorization controls, allowing unauthorized users to potentially access or perform privileged operations within the database management interface.

MitigationUpgrade iotdb-web-workbench to version 0.13.3 or later. This is an optional component, so ensure the specific web-workbench package is updated in addition to any core IoTDB updates.

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, < 0.13.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 iotdb-web-workbench is deployed
    Check for the presence of the web-workbench web application directory, JAR file, or running service. Common locations include the 'web-workbench' folder in the IoTDB installation directory, or look for processes/ports associated with the web console (typically runs on port 9877 or 8080).
    Affected if The web-workbench component is installed or running alongside Apache IoTDB.
  2. Locate the web-workbench version file
    In the IoTDB installation directory, navigate to the web-workbench folder and locate the version identifier. This is typically found in a 'version' file, 'package.json', or the JAR/WAR file name itself. Alternatively, check the application's about/help page if the web UI is accessible.
    Affected if Unable to locate a version file indicates the component may not be present or may be a custom deployment.
  3. Compare installed version to affected range
    Read the identified version number and compare it to the vulnerable range: 0.13.0, 0.13.1, 0.13.2 (any version >= 0.13.0 but < 0.13.3 is affected).
    Affected if The installed version is 0.13.0, 0.13.1, or 0.13.2.
  4. Verify web console authentication enforcement
    If the web-workbench is accessible, attempt to access protected endpoints or privileged operations without valid credentials. Check if the authorization mechanism properly rejects unauthenticated or unauthorized requests.
    Affected if Unauthenticated or low-privilege users can access privileged operations or sensitive data in the web console.

A user is affected if the iotdb-web-workbench component is installed and its version is 0.13.0, 0.13.1, or 0.13.2.

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
Upgrade available Upgrade to 0.13.3 or later
Fixed in 0.13.3
Interim mitigation

Upgrade iotdb-web-workbench to version 0.13.3 or later. This is an optional component, so ensure the specific web-workbench package is updated in addition to any core IoTDB updates.

Recommended fix High confidence

0.13.3 (iotdb-web-workbench)

  1. 1. Identify current IoTDB version by running 'iotdb --version' or checking the installed version
  2. 2. Backup all IoTDB data, configuration files, and the 'data' and 'logs' directories
  3. 3. Stop all running IoTDB services (including any iotdb-web-workbench instances)
  4. 4. Download Apache IoTDB version 0.13.3 (or iotdb-web-workbench 0.13.3 if using it as a separate component) from the official Apache IoTDB repository: https://iotdb.apache.org/Download/
  5. 5. Install the new version following the standard installation process for your deployment method (binary or source compilation)
  6. 6. Restore your configuration from the backed-up config files, ensuring any security-related configurations are properly set
  7. 7. Start the IoTDB service and verify it runs without errors
  8. 8. Verify the iotdb-web-workbench component is accessible and functioning correctly
Caveat Review the release notes for 0.13.3 to check for any configuration or behavioral changes that may affect your deployment

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

Fix this in Iotdb Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24829 — 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-2023-24829 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