- Microsoft Security Blog warns Kubernetes users about helm graphics with predetermined configurations
- These configurations often come with open ports, weak credentials and other risks.
- Microsoft urges Kubernetes users to review their configuration
Kubernetes rudder graphics can expose data without users knowing that Microsoft safety researchers have warned, urging Kubernetes users to be careful and review the predetermined configuration of their helm graphics.
Kubernetes is an open source platform to automate the implementation, scale and administration of container applications. Helm, on the other hand, is a package administrator that simplifies the implementation and administration of Kubernetic applications using preconfigured templates called Graphics.
It allows users to define, install and update complex kubernetic applications with a minimal manual configuration.
Predetermined configurations
In a new blog post, entitled “The risk of default configuration: how the rudder graphics ready to use can violate their cluster”, authors Michael Katchinskiy, and Yossi Weizman, argued that, in many cases, rudder graphics do not require authentication, they maintain certain open ports and use hard to assess or passwords of hard code.
This happens when helm graphics are implemented with the default configuration, which is often the case with inexperienced cloud users.
“The default settings that lack adequate security controls create a severe security threat,” says the blog. “Without carefully reviewing YAML manifestos and helm graphics, organizations can deploy without knowing that they lack any form of protection, leaving them completely exposed to attackers.”
Katchinskiy and Weizman added that the risk is “particularly worrying” when the applications implemented can consult a confidential API or allow administrative actions. “
They sacrard three cases in which the helm graphics put at risk environments of whole Kubernetes: Apache Pinot, Mesery and Selenium Grid.
The best way to mitigate the risk is to be careful when implementing the helm, not using predetermined configurations, and evaluating the configuration from a security perspective to ensure that it includes authentication and network insulation.
In addition, Microsoft recommends that users make regular scanning for erroneous configurations that can expose interfaces to the public and closely monitor containers for unjustified activities.
Through Bleepingcomputer
