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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.8 · apacheNVD modified 2026-10-25 15:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:iotdb:*:*:*:*:*:*:*:*
References 2
- https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/07/06/12 Mailing List, Third Party Advisory