CVE-2020-15127 Denial of service in Contour

In Contour Ingress controller for Kubernetes before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes...

CVE-2020-15127

Contour (Ingress controller for Kubernetes) prior to version 1.7.0 is affected by a DoS that lets a network attacker shut down all Envoy instances. The vulnerability arises from an unauthenticated /shutdown endpoint on port 8090 of the Envoy pod, which triggers Envoy shutdown and flips the readin...

How To Protect Your Kubernetes Cluster with Wallarm – Running in Production Mode – part 3 of 3

The previous two blog articles in this series describe how to set up Wallarm Ingress controller and configure it so that it can properly allow or block traffic from trusted or suspicious/malicious IP addresses. This is essential to the functionality of Wallarm’s Ingress controller but it isn’t...

How To Protect Your Kubernetes Cluster with Wallarm – Running in Production Mode – part 3 of 3

The previous two blog articles in this series describe how to set up Wallarm Ingress controller and configure it so that it can properly allow or block traffic from trusted or suspicious/malicious IP addresses. This is essential to the functionality of Wallarm’s Ingress controller but it isn’t...

Wallarm Launches Support of Envoy Proxy/ Envoy API Protection

Wallarm can protect North-South API in the applications that use Envoy as an alternative Ingress controller at the front end of a Kubernetes cluster. Wallarm can also protect edge traffic and also East-West Envoy API for Service-Mesh and Istio. The post Wallarm Launches Support of Envoy Proxy/...

Choose the right ingress controller for your Kubernetes environment

Choosing the right ingress controller can help you ensure the right infrastructure, direction, and level of customization. Get the information about ingress controllers you need. The post Choose the right ingress controller for your Kubernetes environment appeared first on Wallarm Blog...

Choose the right ingress controller for your Kubernetes environment

Choosing the right ingress controller can help you ensure the right infrastructure, direction, and level of customization. Get the information about ingress controllers you need. The post Choose the right ingress controller for your Kubernetes environment appeared first on Wallarm Blog...

Wallarm to Sponsor KubeCon + CloudNative Con

If you have not registered yet for the main Kubernetes event in North America which will start on December 10th in Seattle, you may be out of luck. The event is sold out and is only taking the waitlist applications. But if you are going, KubeCon + CloudNativeCon promises to be a treat with the...

Wallarm joins CNCF to promote Kubernetes security

Wallarm has recently joined the Linux Foundation and its sister organization, Cloud Native Computing Foundation. Wallarm will be contributing its AI/ML security expertise within the LF and CNCF communities to support the sustainability and adoption of open source technologies. Wallarm and its...

Wallarm Kubernetes Ingress Controller

Kubernetes is a popular technology which aims to improve how containers, microservices and other distributed components are managed across varied infrastructure. Since it was first announced by Google in 2014, it has grown in adoption and is now one of the leading system for automated deployment...

What’s New in Wallarm Node 2.10

We have recently released a new version of Wallarm Node. After your next update window, you will see some new features your DevOps team is certain to like. Firstly, your monitoring and reporting got a lot livelier. Starting with this version in addition to JSON format metrics can be exported in...

Integer Overflow

github.com/kubernetes/minikube is vulnerable to integer overflows. The library uses a vulnerable version of nginx ingress controller that can cause sensitive information to leak when handling a malicious request. This is related to CVE-2017-7529...