CVE-2022-43766
HIGHCVE-2022-43766 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.apache.iotdb:flink-tsfile-connector. O3 Security confirms whether CVE-2022-43766 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache IoTDB prior to 0.13.3 allows DoS
Real-World Exposure
org.apache.iotdb:flink-tsfile-connector☕org.apache.iotdb:iotdb-server☕org.apache.iotdb:tsfile🐍apache-iotdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Apache IoTDB version 0.12.2 to 0.12.6, 0.13.0 to 0.13.2 are vulnerable to a Denial of Service attack when accepting untrusted patterns for REGEXP queries with Java 8. Users should upgrade to 0.13.3 which addresses this issue or use a later version of Java to avoid it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.iotdb:flink-tsfile-connector | ≥ 0.12.2&&< 0.13.3 | 0.13.3 |
| ☕Maven | org.apache.iotdb:iotdb-server | ≥ 0.12.2&&< 0.13.3 | 0.13.3 |
| ☕Maven | org.apache.iotdb:tsfile | ≥ 0.12.2&&< 0.13.3 | 0.13.3 |
| 🐍PyPI | apache-iotdb | ≥ 0.12.2&&< 0.13.3 | 0.13.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.iotdb:flink-tsfile-connector. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.iotdb:flink-tsfile-connector to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43766 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-43766 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-43766. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-43766 in your dependencies?
O3 detects CVE-2022-43766 across Maven, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.