dbcve.org
IotdbApplication · Apache

CVE-2022-43766

HIGH · 7.5 CVSS v3.1 Published 2022-10-26
Fix available
A fix is available. Upgrade to after 0.13.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache IoTDB versions 0.12.2-0.12.6 and 0.13.0-0.13.2 are vulnerable to Denial of Service when processing untrusted REGEXP query patterns on Java 8, likely due to inefficient regex backtracking or resource exhaustion.

MitigationUpgrade Apache IoTDB to version 0.13.3 or later, or migrate from Java 8 to a newer Java version to resolve the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IotdbApplication
Affected:>= 0.12.2, <= 0.12.6>= 0.13.0, <= 0.13.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache IoTDB version
    Run the iotdb version command, or check the release information in the iotdb-common JAR's MANIFEST.MF file, or inspect the start script output for version info
    Affected if The installed version is >= 0.12.2 and <= 0.12.6, OR >= 0.13.0 and <= 0.13.2
  2. Verify Java runtime version in use
    Run 'java -version' from the command line, or check the JAVA_HOME environment variable and the Java version configured in iotdb-env.sh or the startup scripts
    Affected if The Java runtime is version 8 (1.8.x)
  3. Confirm REGEXP query functionality is accessible
    Inspect the iotdb-common.properties or iotdb-engine.properties configuration file for the enable_regexp parameter, or check if REGEXP function is enabled in the query processor settings
    Affected if REGEXP query processing is enabled (either explicitly or by default) and untrusted input can reach the REGEXP query parser

You are affected if your environment runs Apache IoTDB version 0.12.2-0.12.6 or 0.13.0-0.13.2 on Java 8 with REGEXP query functionality accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.13.2
Interim mitigation

Upgrade Apache IoTDB to version 0.13.3 or later, or migrate from Java 8 to a newer Java version to resolve the vulnerability.

Recommended fix High confidence

0.13.3 or later (e.g., latest 0.13.x or 1.x release)

  1. 1. Back up your existing IoTDB data, configuration files, and any custom scripts
  2. 2. Verify your current Java version by running 'java -version'; if using Java 8, plan to upgrade to Java 11 or later as an alternative mitigation
  3. 3. Stop the IoTDB service gracefully
  4. 4. Download Apache IoTDB version 0.13.3 (or latest 0.13.x/1.x version) from the official Apache IoTDB repository at https://iotdb.apache.org/
  5. 5. Install the new version following the official installation guide
  6. 6. Restore your configuration files from the backup (or reconfigure as needed)
  7. 7. Start the IoTDB service
  8. 8. Validate that REGEXP queries work correctly and the service is stable
Caveat Review release notes between your current version and 0.13.3 for any configuration or API changes; minor version upgrades typically maintain backward compatibility but testing is recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iotdb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43766 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data