CVE-2020-1952 Improper Certificate Validation in Apache IoTDB

Critical 9.8 Published Updated

Attackers can execute arbitrary code remotely via the exposed JMX port due to lack of authentication in Apache IoTDB.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2020-1952?

CVE-2020-1952 is a critical missing authorization vulnerability in Apache IoTDB, published on 27 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-295

Which versions are affected by CVE-2020-1952?

2 open source packages ship an affected version, including org.apache.iotdb:iotdb-parent. It affects 1 product.

PackageAffectedFixed in
org.apache.iotdb:iotdb-parent MavenAll versions0.9.2
org.apache.iotdb:iotdb-parent MavenAll versions0.9.2

Products include Apache Iotdb.

How do I fix CVE-2020-1952?

Upgrade org.apache.iotdb:iotdb-parent to 0.9.2 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2020-1952 being exploited?

There is no known exploitation of CVE-2020-1952 in the wild and no public exploit code.

Sources

Also known as GHSA-wc6f-cjcp-cc33.

Is CVE-2020-1952 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free