Not rated
CVE-2026-24014 Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to…
Description
Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Apache IoTDB 1.3 | 1.3.3 → < 2.0.8 | 2.0.8 |
References
- lists.apache.org lists.apache.org
Timeline
- Published
- Last modified
Other CVEs of Apache IoTDB
The 28 CVEs of Apache IoTDB →
CVE-2026-59229
The Legacy Pipe receiver protocol (handshake / sendPipeData) uses a hardcoded SUPER_USER (root) identity when…
Not rated
CVE-2026-59562
Missing authentication for critical function vulnerability in Apache IoTDB
Not rated
CVE-2026-58663
An authentication bypass vulnerability exists in Apache IoTDB's Thrift RPC service This issue affects Apache IoTDB: from…
Not rated
CVE-2026-44630
Improper validation of length fields in the Apache IoTDB RPC service may allow a remote unauthenticated attacker to…
Not rated