REDHAT-BUG-2433786: High severity github/theforeman/foreman_kubevirt vulnerability
Summary: MITM in foremankubevirt due to insecure defaults
Requirements to exploit: Being able to MITM traffic between Satellite and OpenShift
Component affected: https://github.com/theforeman/foremankubevirt
Version affected: <= 0.4.0
Patch available: no
Version fixed (if any already): N/A
CVSS (optional): N/A
Impact (optional): Important
Embargo: No
Reason: The amount of affected systems should be low Suggested public date: dd-MMM-yyyy
Acknowledgement: Evgeni Golov
Steps to reproduce if available:
Configure OpenShift Virtualization / KubeVirt in Satellite and don't enter anything in the CA field Mitigation if available: Explicitly set a CA
Original report: this email
When foremankubevirt configures the connection to OpenShift, it only enables kubevirtverifyssl when a CA certificate was explicitly set in the settings [1]. Normally, users would expect that the system trust store is used when no explicit CA was set. But in this case the whole verification is disabled instead.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using foreman_kubevirt version 0.4.0 or earlier to configure an OpenShift Virtualization or KubeVirt connection in Satellite are exposed when the CA field is left empty. The reported number of affected systems is expected to be low.
What access does an attacker need?
An attacker must be able to perform a man-in-the-middle attack on traffic between Satellite and OpenShift.
Does leaving the CA field blank use the system trust store?
No. In the affected configuration, leaving the CA field blank disables SSL verification rather than using the system trust store.
What can be done if an update is not available?
Explicitly configure a CA certificate in the relevant CA field. This causes certificate verification to be enabled for the OpenShift connection.
How can I identify an affected configuration?
Check whether foreman_kubevirt is version 0.4.0 or earlier and whether its OpenShift Virtualization or KubeVirt connection has no CA configured. A blank CA field is the condition that disables verification.