Tuesday, December 3, 2024
Homecyber securityOver 380 000 Kubernetes API Servers are Exposed to a Range of...

Over 380 000 Kubernetes API Servers are Exposed to a Range of Attacks

Published on

SIEM as a Service

Kubernetes is an open-source container orchestration system for automating software deployment, scaling, and management.

The Shadowserver Foundation started scanning for accessible Kubernetes API instances that respond with a 200 OK HTTP response to the probes.

“We find over 380 000 Kubernetes API daily that allows for some form of access, out of over 450 000 that we are able to identify. Data on these is shared daily in our Accessible Kubernetes API Server Report.”, reads the post published by Shadowserver Foundation.

- Advertisement - SIEM as a Service

The result of the scan does not mean these servers are fully open or vulnerable to attacks, it suggests a situation where the servers have an “unnecessarily exposed attack surface”.

They scan all of the IPv4 space on ports 6443 and 443 and include only Kubernetes servers that respond with a 200 OK (with accompanying JSON response), and hence disclose version information in their response.

The post says, “A scan result for 2022-05-16 uncovers 381,645 unique IPs responding with a 200 OK HTTP response to our probes”.

“This is out of the 454,729 Kubernetes API instances we see. The “open” API instances thus constitute nearly 84% of all instances that we can scan for on the Ipv4 Internet.”

Erfan Shadabi, the cyber-security expert with data-security firm Comforte AG, stated that he was unsurprised that the Shadowserver scan discovered so many Kubernetes servers exposed to the public internet.

“White Kubernetes] provides massive benefits to enterprises for agile app delivery, there are a few characteristics that make it an ideal attack target for exploitation”.

“For instance, as a result of having many containers, Kubernetes has a large attack surface that could be exploited if not pre-emptively secured”, he stated.

Protecting Kubernetes

Shadowserver advises that if administrators find that a Kubernetes instance in their environment is accessible to the internet, they should consider implementing ‘authorisation for access,’ or block at the firewall level to reduce the attack surface exposed.

Also, if your Kubernetes API endpoint is available on an IP you were not expecting, and you use kube-proxy in IPVS mode see https[:]//github.com/kubernetes/kubernetes/pull/108460.

Erfan Shadabi suggests that organizations that use containers and Kubernetes in their production environment are to take securing Kubernetes as seriously as they do all aspects of their IT infrastructure.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

PEFT-As-An-Attack, Jailbreaking Language Models For Malicious Prompts

Federated Parameter-Efficient Fine-Tuning (FedPEFT) is a technique that combines parameter-efficient fine-tuning (PEFT) with federated...

Hackers Cloning Websites, Exploiting RCE Flaws To Gain Access To Shopping Platforms

Cybercriminals are leveraging AI-powered phishing attacks, website cloning tools, and RCE exploits to target...

Hackers Exploited Windows Event Logs Tool log Manipulation, And Data Exfiltration

wevtutil.exe, a Windows Event Log management tool, can be abused for LOLBAS attacks. By...

Threat Actors Allegedly Claims Breach of EazyDiner Reservation Platform

Reports have emerged of a potential data breach involving EazyDiner, a leading restaurant reservation...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

PEFT-As-An-Attack, Jailbreaking Language Models For Malicious Prompts

Federated Parameter-Efficient Fine-Tuning (FedPEFT) is a technique that combines parameter-efficient fine-tuning (PEFT) with federated...

Hackers Cloning Websites, Exploiting RCE Flaws To Gain Access To Shopping Platforms

Cybercriminals are leveraging AI-powered phishing attacks, website cloning tools, and RCE exploits to target...

Hackers Exploited Windows Event Logs Tool log Manipulation, And Data Exfiltration

wevtutil.exe, a Windows Event Log management tool, can be abused for LOLBAS attacks. By...