During an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.
Impact
All users on release v0.12.2 and before are affected.
Patches
This issue was fixed by PR #1217, users should upgrade to latest release.
Workarounds
Add automountServiceAccountToken: false to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the CONSOLE_IDP_URL, CONSOLE_IDP_CLIENT_ID, CONSOLE_IDP_SECRET and CONSOLE_IDP_CALLBACK environment variable and instead use the Kubernetes service account token.
References
#1217 for more information on the fix and how it was fixed.
For more information
If you have any questions or comments about this advisory:
During an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.
Impact
All users on release v0.12.2 and before are affected.
Patches
This issue was fixed by PR #1217, users should upgrade to latest release.
Workarounds
Add
automountServiceAccountToken: falseto the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset theCONSOLE_IDP_URL,CONSOLE_IDP_CLIENT_ID,CONSOLE_IDP_SECRETandCONSOLE_IDP_CALLBACKenvironment variable and instead use the Kubernetes service account token.References
#1217 for more information on the fix and how it was fixed.
For more information
If you have any questions or comments about this advisory: