dbcve.org
Iotdb WorkbenchApplication · Apache

CVE-2024-36448

HIGH · 7.3 CVSS v3.1 Published 2024-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
** UNSUPPORTED WHEN ASSIGNED ** Server-Side Request Forgery (SSRF) vulnerability in Apache IoTDB Workbench. This issue affects Apache IoTDB Workbench: from 0.13.0. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 Workbench versions 0.13.0 and later contain a Server-Side Request Forgery (SSRF) vulnerability allowing attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This can enable access to internal services, cloud metadata endpoints, or firewall-protected systems. The vulnerability carries a CVSS score of 7.3 (HIGH).

MitigationSince Apache IoTDB Workbench is retired with no patch forthcoming, organizations should either migrate to an alternative solution or implement strict network segmentation and access controls to limit exposure to trusted users only.

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
Iotdb WorkbenchApplication
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
Low
Integrity
Low
Availability
Low

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

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 Apache IoTDB Workbench is installed
    Look for the IoTDB Workbench service/process on the system, or check for its web application files in common installation directories
    Affected if The software is present on the system
  2. Determine the installed version
    Check the version of Apache IoTDB Workbench by inspecting the application metadata, about page, or package files
    Affected if The version is 0.13.0 or higher (any version from 0.13.0 onwards)
  3. Verify web interface exposure
    Check if the Workbench web interface is accessible from untrusted networks by reviewing firewall rules, reverse proxy configurations, or network ACLs
    Affected if The interface is reachable from external or untrusted networks without proper access controls
  4. Review application logs for SSRF indicators
    Examine web server and application logs for suspicious URL patterns, requests to internal IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x), or cloud metadata endpoints (169.254.169.254)
    Affected if Log entries show requests to internal resources initiated by the application that were not internally generated

If Apache IoTDB Workbench version 0.13.0 or higher is installed and its web interface is network-accessible, the system is affected by this SSRF vulnerability.

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

Since Apache IoTDB Workbench is retired with no patch forthcoming, organizations should either migrate to an alternative solution or implement strict network segmentation and access controls to limit exposure to trusted users only.

Recommended fix High confidence
  1. 1. Assess whether Apache IoTDB Workbench is actively needed in your environment.
  2. 2. Since the project is retired with no planned fixes, evaluate alternative solutions that are actively maintained.
  3. 3. If continued use is unavoidable, implement strict network access controls: restrict the Workbench interface to trusted IP addresses only, ideally through firewall rules or network segmentation.
  4. 4. Disable the Workbench service if not actively required.
  5. 5. Monitor for any unauthorized access attempts to the affected instance.
Caveat This is a retired project with no upgrade path; migration to an alternative solution will be required.

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

Fix this in Iotdb Workbench Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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