dbcve.org
IotdbApplication · Apache

CVE-2024-24780

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Remote Code Execution with untrusted URI of UDF vulnerability in Apache IoTDB. The attacker who has privilege to create UDF can register malicious function from untrusted URI. This issue affects Apache IoTDB: from 1.0.0 before 1.3.4. Users are recommended to upgrade to version 1.3.4, which fixes the 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 allows users with UDF creation privileges to register functions from external URIs. An attacker with this privilege can specify a malicious URI, causing the system to load and execute arbitrary code remotely, achieving remote code execution.

MitigationUpgrade Apache IoTDB to version 1.3.4 or later. Until then, restrict UDF creation privileges to trusted administrators 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
IotdbApplication
Affected:>= 1.0.0, < 1.3.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Apache IoTDB version
    Run 'iotdb --version' or check the iotdb classpath/version file in the installation directory. Compare the version number against the affected range >=1.0.0 and <1.3.4.
    Affected if The installed version is 1.0.0, 1.1.x, 1.2.x, or 1.3.0 through 1.3.3.
  2. Verify UDF creation privilege configuration
    Inspect the user permission configuration in the IoTDB authorization system. Check if any non-administrator users have been granted UDF creation or UDF registration privileges.
    Affected if Non-trusted or low-privilege users possess UDF creation or UDF registration permissions.
  3. Confirm UDF external URI loading is enabled
    Check the IoTDB configuration file (iotdb-common.properties or iotdb-config.properties) for settings controlling UDF URI loading. Look for properties like 'udf_enable_external_uri' or similar that control whether UDFs can be loaded from external URIs.
    Affected if External URI loading for UDFs is permitted in the configuration.
  4. Audit existing UDF registrations for external URIs
    Query the IoTDB system catalog or UDF metadata using the SHOW FUNCTIONS command. Inspect any registered UDFs to identify if they were loaded from external URIs rather than being built-in or locally registered.
    Affected if Any UDF is registered with an external (http, https, ftp, or other remote URI) source location.

You are affected if your IoTDB version is between 1.0.0 and 1.3.3 inclusive AND non-administrator users have UDF creation privileges AND external URI loading is enabled for UDFs.

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 1.3.4 or later
Fixed in 1.3.4
Interim mitigation

Upgrade Apache IoTDB to version 1.3.4 or later. Until then, restrict UDF creation privileges to trusted administrators only.

Recommended fix High confidence

1.3.4

  1. 1. Stop all running IoTDB services and ensure no active connections
  2. 2. Back up your existing IoTDB configuration, data directory, and any custom scripts
  3. 3. Download Apache IoTDB version 1.3.4 from the official Apache IoTDB downloads page (https://iotdb.apache.org/Download/)
  4. 4. Install version 1.3.4 following the standard IoTDB installation procedure for your deployment type
  5. 5. Restore your backed-up configuration files to the new installation
  6. 6. Verify file permissions are correctly set for the new installation
  7. 7. Start the IoTDB service and confirm it runs without errors
  8. 8. If you have UDFs, review and re-register any user-defined functions using trusted, verified URIs
Caveat Review the 1.3.4 release notes for any configuration or behavioral changes from your current version

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

Fix this in Iotdb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA4.0 h
25.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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