CVE-2020-3943

CVE-2020-3943 is a critical-severity vulnerability in Vmware Vrealize Operations 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.

Key facts

Description

vRealize Operations for Horizon Adapter (6.7.x prior to 6.7.1 and 6.6.x prior to 6.6.1) uses a JMX RMI service which is not securely configured. An unauthenticated remote attacker who has network access to vRealize Operations, with the Horizon Adapter running, may be able to execute arbitrary code in vRealize Operations.

Frequently asked questions

What is CVE-2020-3943?
vRealize Operations for Horizon Adapter (6.7.x prior to 6.7.1 and 6.6.x prior to 6.6.1) uses a JMX RMI service which is not securely configured. An unauthenticated remote attacker who has network access to vRealize Operations, with the Horizon Adapter running, may be able to execute arbitrary code in vRealize Operations.
How severe is CVE-2020-3943?
CVE-2020-3943 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-3943 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-3943?
CVE-2020-3943 affects Vmware Vrealize Operations. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-3943?
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-3943 published?
CVE-2020-3943 was published on 2020-02-19 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Vmware Vrealize Operations

All CVEs affecting Vmware Vrealize Operations →