CVE-2019-3899

CVE-2019-3899 is a critical-severity vulnerability in Redhat Openshift Container Platform 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-592.

Key facts

Description

It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.

Frequently asked questions

What is CVE-2019-3899?
It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.
How severe is CVE-2019-3899?
CVE-2019-3899 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-2019-3899 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-3899?
CVE-2019-3899 primarily affects Redhat Openshift Container Platform. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-3899?
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-2019-3899 published?
CVE-2019-3899 was published on 2019-04-22 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Redhat Openshift Container Platform

All CVEs affecting Redhat Openshift Container Platform →

Other CWE-592 vulnerabilities

Browse all CWE-592 vulnerabilities →