dbcve.org
IotdbApplication · Apache

CVE-2020-1952

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-27
Fix available
A fix is available. Upgrade to after 0.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was found in Apache IoTDB .9.0 to 0.9.1 and 0.8.0 to 0.8.2. When starting IoTDB, the JMX port 31999 is exposed with no certification.Then, clients could execute code remotely.

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.9.0-0.9.1 and 0.8.0-0.8.2 expose JMX port 31999 without authentication or certification when the service starts. This allows unauthenticated remote attackers to interact with the JMX interface and execute arbitrary code remotely.

MitigationBind JMX to localhost only, enable JMX authentication with proper credentials, or block external access to port 31999 via firewall/network segmentation.

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.8.0, <= 0.8.2>= 0.9.0, <= 0.9.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 'iotdb version' from the IoTDB installation directory, or check the release notes or about page in the IoTDB web interface if available
    Affected if Version is 0.8.0-0.8.2 or 0.9.0-0.9.1
  2. Verify if JMX port 31999 is listening
    Run 'netstat -an | grep 31999' or 'ss -tlnp | grep 31999' to check if port 31999 is open and listening
    Affected if Port 31999 is in LISTEN state and bound to an interface accessible from outside localhost
  3. Determine JMX port network binding
    Check the network configuration - if bound to 0.0.0.0 or the external IP rather than 127.0.0.1, it is externally accessible. Use 'netstat -tlnp' to see the binding address
    Affected if Port 31999 is bound to 0.0.0.0 or a non-localhost IP address
  4. Check if JMX authentication is disabled
    Inspect the IoTDB startup scripts (start.bat, start.sh, or iotdb-env.sh) and configuration files (iotdb-env.sh, iotdb-config.properties) for JMX-related settings. Look for com.sun.management.jmxremote.authenticate=false or similar flags
    Affected if JMX authentication is explicitly disabled or no credentials are configured in the JMX settings
  5. Test external access to JMX port
    From a remote machine, attempt to connect to the target server on port 31999 using an LDAP lookup tool or JMX client such as 'nc -zv <target_ip> 31999' or by attempting a JMX connection
    Affected if Port 31999 is reachable from external hosts and accepts JMX connections without authentication

A user is affected if they run Apache IoTDB versions 0.8.0-0.8.2 or 0.9.0-0.9.1 with JMX port 31999 exposed and accessible externally without authentication enabled.

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.9.1
Interim mitigation

Bind JMX to localhost only, enable JMX authentication with proper credentials, or block external access to port 31999 via firewall/network segmentation.

Recommended fix High confidence

Apache IoTDB 0.9.2 (if on 0.9.x) or Apache IoTDB 0.8.3 (if on 0.8.x)

  1. 1. Identify your current Apache IoTDB version using 'ls -la' in the IoTDB installation directory or checking the version flag
  2. 2. If running version 0.9.0 or 0.9.1: Stop the IoTDB service completely
  3. 3. If running version 0.8.0, 0.8.1, or 0.8.2: Stop the IoTDB service completely
  4. 4. Back up your IoTDB data directory and configuration files (especially iotdb-engine.properties and iotdb-env.sh)
  5. 5. Download Apache IoTDB version 0.9.2 (for 0.9.x users) or version 0.8.3 (for 0.8.x users) from the official Apache IoTDB releases page at https://iotdb.apache.org/Download/
  6. 6. Extract the new version to a clean directory
  7. 7. Copy your backed-up configuration files to the new installation, reviewing for any deprecated settings
  8. 8. Start the IoTDB service with the new version
Caveat Review release notes for any breaking changes between your current version and the target version; minor version upgrades within the same branch typically have minimal breaking changes

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1952 — 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-2020-1952 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