Friday, February 28, 2025
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

Follow Us on Google News

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.

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

Chinese Hackers Exploit Check Point VPN Zero-Day to Target Organizations Globally

A sophisticated cyberespionage campaign linked to Chinese state-sponsored actors has exploited a previously patched...

PingAM Java Agent Vulnerability Allows Attackers to Bypass Security

A critical security flaw (CVE-2025-20059) has been identified in supported versions of Ping Identity’s...

New GitHub Scam Uses Fake “Mods” and “Cracks” to Steal User Data

A sophisticated malware campaign leveraging GitHub repositories disguised as game modifications and cracked software...

260 Domains Hosting 5,000 Malicious PDFs to Steal Credit Card Data

Netskope Threat Labs uncovered a sprawling phishing operation involving 260 domains hosting approximately 5,000...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Chinese Hackers Exploit Check Point VPN Zero-Day to Target Organizations Globally

A sophisticated cyberespionage campaign linked to Chinese state-sponsored actors has exploited a previously patched...

PingAM Java Agent Vulnerability Allows Attackers to Bypass Security

A critical security flaw (CVE-2025-20059) has been identified in supported versions of Ping Identity’s...

New GitHub Scam Uses Fake “Mods” and “Cracks” to Steal User Data

A sophisticated malware campaign leveraging GitHub repositories disguised as game modifications and cracked software...