CVE-2026-24014: CWE-284 Improper Access Control in Apache Software Foundation Apache IoTDB
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.
AI Analysis
Technical Summary
Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to construct a file path without sufficient validation. If the internal RPC port is exposed to an untrusted network, an attacker can exploit path traversal sequences in the JAR name to write files outside the designated Trigger installation directory. This vulnerability affects Apache IoTDB versions from 1.3.3 before 2.0.8. The vendor recommends upgrading to version 2.0.8 to remediate this issue.
Potential Impact
An attacker with access to the internal DataNode RPC port can write arbitrary files on the system running Apache IoTDB with the same permissions as the IoTDB process. This could lead to unauthorized file modification or code execution depending on the environment and permissions.
Mitigation Recommendations
Users should upgrade Apache IoTDB to version 2.0.8 or later, which contains the fix for this vulnerability. There is no indication of alternative mitigations or temporary fixes. Restricting access to the internal DataNode RPC port to trusted networks can reduce exposure.
CVE-2026-24014: CWE-284 Improper Access Control in Apache Software Foundation Apache IoTDB
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.
CVSS v3.1
Score 9.8critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to construct a file path without sufficient validation. If the internal RPC port is exposed to an untrusted network, an attacker can exploit path traversal sequences in the JAR name to write files outside the designated Trigger installation directory. This vulnerability affects Apache IoTDB versions from 1.3.3 before 2.0.8. The vendor recommends upgrading to version 2.0.8 to remediate this issue.
Potential Impact
An attacker with access to the internal DataNode RPC port can write arbitrary files on the system running Apache IoTDB with the same permissions as the IoTDB process. This could lead to unauthorized file modification or code execution depending on the environment and permissions.
Mitigation Recommendations
Users should upgrade Apache IoTDB to version 2.0.8 or later, which contains the fix for this vulnerability. There is no indication of alternative mitigations or temporary fixes. Restricting access to the internal DataNode RPC port to trusted networks can reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-01-20T03:04:59.061Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b6caa27e9c797192521ad
Added to database: 07/06/2026, 08:51:54 UTC
Last enriched: 07/06/2026, 09:22:36 UTC
Last updated: 07/07/2026, 02:45:53 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.