424 matches found
PYSEC-2026-2079
Uncontrolled Resource Consumption vulnerability in Apache IoTDB. Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters e.g., a very large time range combined with a minimal interval. Thi...
CVE-2026-24012
Uncontrolled Resource Consumption vulnerability in Apache IoTDB. Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters e.g., a very large time range combined with a minimal interval. Thi...
CVE-2026-24013
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
PYSEC-2026-2081
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 t...
PYSEC-2026-2079
Uncontrolled Resource Consumption vulnerability in Apache IoTDB.Some interfacefails to impose reasonablelimits on the time span and aggregation interval of the query.An attackercan construct a request with extreme parameters e.g., a very large timerange combined with a minimal interval.This force...
syunity-meteo (0.1.0) potentially affected by CVE-2026-24013 via apache-iotdb (1.3.4)
apache-iotdb PYPI version 1.3.4 is affected by a known vulnerability. The following packages have a transitive dependency on apache-iotdb and may be impacted: - syunity-meteo 0.1.0 Source cves: CVE-2026-24013 Source advisory: OSV:PYSEC-2026-2080...
CVE-2026-24013 Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
CVE-2026-24013
Apache IoTDB versions 1.3.3 through 2.0.7 are vulnerable to an Authentication Bypass by Spoofing vulnerability. The root cause is the lack of strict validation of the sessionId parameter within certain Thrift RPC query handlers . An attacker can construct requests with a forged sessionId to bypas...
CVE-2026-24013
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
CVE-2026-24013
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
CVE-2026-24013 Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
EUVD-2026-41857
Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This...
org.apache.iotdb:customize-mqtt-example (>=1.3.3, <=2.0.1-beta), org.apache.iotdb:integration-test (>=1.3.3, <=2.0.1-beta) +6 more potentially affected by CVE-2026-24013 via org.apache.iotdb:iotdb-server (>=1.3.3, <=2.0.1-beta)
org.apache.iotdb:iotdb-server MAVEN version =1.3.3, =1.3.3, =1.3.3, =1.3.3, =1.3.3, =1.3.3, =1.3.3, =1.3.3, =2.0.1-beta - org.apache.iotdb:udf-example 1.3.3 Source cves: CVE-2026-24013 Source advisory: MEND:CVE-2026-24013...
CVE-2026-24012
Apache IoTDB (versions 1.3.3 through 2.0.7 ) is vulnerable to an Uncontrolled Resource Consumption vulnerability in its aggregation query interface. The root cause is a failure to impose reasonable limits on the time span and aggregation interval of queries. An attacker can exploit this by constr...
CVE-2026-24012 Apache IoTDB: Denial of Service via Resource Exhaustion in Aggregation Query
Uncontrolled Resource Consumption vulnerability in Apache IoTDB. Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters e.g., a very large time range combined with a minimal interval. Thi...
EUVD-2026-41856
Uncontrolled Resource Consumption vulnerability in Apache IoTDB. Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters e.g., a very large time range combined with a minimal interval. Thi...
CVE-2026-24014 Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write
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 t...
EUVD-2026-41854
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 t...
CVE-2026-24014
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 t...
CVE-2026-24014
Apache IoTDB versions 1.3.3 through 2.0.7 are vulnerable to a path traversal vulnerability in the DataNode’s internal RPC interface. When creating Trigger instances, the system fails to sufficiently validate the name of the uploaded Trigger JAR when constructing a file path. If the internal DataN...