CVE-2020-1952: Improper Certificate Validation in Apache IoTDB

CVE-2020-1952 · Severity: low · CVSS 3.1 · Published 2022-01-06

Improper Certificate Validation in Apache IoTDB

Technologies: org.apache.iotdb:iotdb-parent (Maven). Vendors: Maven.

Quick answers

Is CVE-2020-1952 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-1952 being exploited in the wild.
How severe is CVE-2020-1952?
Low severity, with a CVSS score of 3.1, published 6 January 2022.
Which products and versions are affected?
org.apache.iotdb:iotdb-parent (Maven) ECOSYSTEM:introduced=0,fixed=0.9.2.
Is there a fix for CVE-2020-1952?
Yes. org.apache.iotdb:iotdb-parent (Maven): upgrade to 0.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-1952?
Check whether you run org.apache.iotdb:iotdb-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.iotdb:iotdb-parent (Maven): upgrade to 0.9.2 or later
    # set org.apache.iotdb:iotdb-parent to 0.9.2 in your pom.xml or build.gradle

Affected products

  • org.apache.iotdb:iotdb-parent (Maven) ECOSYSTEM:introduced=0,fixed=0.9.2

Identifiers

  • CVE-2020-1952
  • GHSA-wc6f-cjcp-cc33

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.