CVE-2020-1952
CRITICALCVSS 9.8/10EPSS 2.68%
Last modified
CVE-2020-1952 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 2.68% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Iotdb | >= 0.8.0, <= 0.8.2 |
| Apache | Iotdb | >= 0.9.0, <= 0.9.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
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 score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 2.68% probability of exploitation in the next 30 days.
How do I fix CVE-2020-1952?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2020-1952?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST