### Summary Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process. ### Affected Apache IoTDB **from 1.0.0 before 2.0.5**. ### Remediation Upgrade to **2.0.5**, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted networks and disable or sanitize any feature paths that accept serialized payloads. These mitigations are defense-in-depth only; upgrading to 2.0.5 is the definitive fix.
Update org.apache.iotdb:iotdb-confignode to 2.0.5; apache-iotdb to 2.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache IoTDB: Deserialization of untrusted Data affects org.apache.iotdb:iotdb-confignode (maven), apache-iotdb (pip). Severity is critical. ### Summary Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process. ### Affected Apache IoTDB **from 1.0.0 before 2.0.5**. ### Remediation Upgrade to **2.0.5**, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted networks and disable or sanitize any feature paths that accept serialized payloads. These mitigations are defense-in-depth only; upgrading to 2.0.5 is the definitive fix.
AI coding agents often install or upgrade packages automatically in maven and pip. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
### Summary Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process. ### Affected Apache IoTDB **from 1.0.0 before 2.0.5**. ### Remediation Upgrade to **2.0.5**, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted networks and disable or sanitize any feature paths that accept serialized payloads. These mitigations are defense-in-depth only; upgrading to 2.0.5 is the definitive fix.
Update org.apache.iotdb:iotdb-confignode to 2.0.5; apache-iotdb to 2.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache IoTDB: Deserialization of untrusted Data affects org.apache.iotdb:iotdb-confignode (maven), apache-iotdb (pip). Severity is critical. ### Summary Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process. ### Affected Apache IoTDB **from 1.0.0 before 2.0.5**. ### Remediation Upgrade to **2.0.5**, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted networks and disable or sanitize any feature paths that accept serialized payloads. These mitigations are defense-in-depth only; upgrading to 2.0.5 is the definitive fix.
AI coding agents often install or upgrade packages automatically in maven and pip. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
| org.apache.iotdb:iotdb-confignodemaven | >=1.0.0,<2.0.5 | 2.0.5 |
|---|---|---|
| apache-iotdbpip | >=1.0.0,<2.0.5 | 2.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| org.apache.iotdb:iotdb-confignodemaven | >=1.0.0,<2.0.5 | 2.0.5 |
|---|---|---|
| apache-iotdbpip | >=1.0.0,<2.0.5 | 2.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard