# CVE-2024-36448: Apache IoTDB Workbench: SSRF Vulnerability (EOL)

> Server-Side Request Forgery in Apache IoTDB Workbench allows attackers to interact with internal resources; the project is retired with no fix available.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-5hj8-xgx5-p37f

## What is CVE-2024-36448?

CVE-2024-36448 is a high-severity server-side request forgery vulnerability in Apache IoTDB Workbench, published on 5 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

** 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-36448?

It affects 1 product.


Products: Apache Iotdb Workbench.

## How do I fix CVE-2024-36448?

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

## Is CVE-2024-36448 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36448 and fix it if it is affected.

What it is: CVE-2024-36448 is a high-severity server-side request forgery vulnerability in Apache IoTDB Workbench, published on 5 Aug 2024. 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-2024-36448 in the wild and no public exploit code.

Affected product: Apache IoTDB Workbench. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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