How severe is CVE-2020-1952?

CVE-2020-1952 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-1952 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-1952?

CVE-2020-1952 affects Apache Iotdb. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-1952?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-1952 published?

CVE-2020-1952 was published on 2020-04-27 and last updated on 2026-06-17.

CVE-2020-1952

CVE-2020-1952 is a critical-severity vulnerability in Apache Iotdb with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-295
Affected product: Apache Iotdb
Published: 2020-04-27
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2020-1952?: 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.
How severe is CVE-2020-1952?: CVE-2020-1952 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-1952 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-1952?: CVE-2020-1952 affects Apache Iotdb. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-1952?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-1952 published?: CVE-2020-1952 was published on 2020-04-27 and last updated on 2026-06-17.

References

https://lists.apache.org/thread.html/r3d2ff899ead64d2952fdc1fbb1f520ca42011ed2b4c7f786e921f6b9%40%3Cdev.iotdb.apache.org%3E

Affected products (1)

cpe:2.3:a:apache:iotdb:*:*:*:*:*:*:*:*

More vulnerabilities in Apache Iotdb

CVE-2026-24014 — Critical (CVSS 9.8): Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to…
CVE-2026-24713 — Critical (CVSS 9.8): Improper Input Validation vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7,…
CVE-2026-24015 — Critical (CVSS 9.8): A vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before…
CVE-2024-24780 — Critical (CVSS 9.8): Remote Code Execution with untrusted URI of UDF vulnerability in Apache IoTDB. The attacker who has privilege to…
CVE-2023-46226 — Critical (CVSS 9.8): Remote Code Execution vulnerability in Apache IoTDB.This issue affects Apache IoTDB: from 1.0.0 through 1.2.2. Users…
CVE-2023-51656 — Critical (CVSS 9.8): Deserialization of Untrusted Data vulnerability in Apache IoTDB.This issue affects Apache IoTDB: from 0.13.0 through…

All CVEs affecting Apache Iotdb →

Other CWE-295 (Improper Certificate Validation) vulnerabilities

CVE-2026-4370 — Critical (CVSS 10.0): A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the…
CVE-2026-30836 — Critical (CVSS 10.0): Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6…
CVE-2025-68121 — Critical (CVSS 10.0): During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…
CVE-2022-20703 — Critical (CVSS 10.0): Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker…
CVE-2021-1471 — Critical (CVSS 9.9): Multiple vulnerabilities in Cisco Jabber for Windows, Cisco Jabber for MacOS, and Cisco Jabber for mobile platforms…
CVE-2026-20184 — Critical (CVSS 9.8): A vulnerability in the integration of single sign-on (SSO) with Control Hub in Cisco Webex Services could have allowed…

Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →