GitBook: [#3068] No subject

pentesting/pentesting-kubernetes/attacking-kubernetes-from-inside-a-pod.md

@@ -83,9 +83,18 @@ Check out the following page to learn how you could **attack Kubernetes specific
 
 ### Sniffing
 
-In case the **compromised pod is running some sensitive service** where other pods need to authenticate you might be able to obtain the credentials send from the other pods.
+In case the **compromised pod is running some sensitive service** where other pods need to authenticate you might be able to obtain the credentials send from the other pods **sniffing local communications**.
 
-### Node DoS
+## Network Spoofing
+
+By default techniques like **ARP spoofing** (and thanks to that **DNS Spoofing**) work in kubernetes network. Then, inside a pod, if you have the **NET\_RAW capability** (which is there by default), you will be able to send custom crafted network packets and perform **MitM attacks via ARP Spoofing to all the pods running in the same node.**\
+****Moreover, if the **malicious pod** is running in the **same node as the DNS Server**, you will be able to perform a **DNS Spoofing attack to all the pods in cluster**.
+
+{% content-ref url="../../cloud-security/pentesting-kubernetes/kubernetes-network-attacks.md" %}
+[kubernetes-network-attacks.md](../../cloud-security/pentesting-kubernetes/kubernetes-network-attacks.md)
+{% endcontent-ref %}
+
+## Node DoS
 
 There is no specification of resources in the Kubernetes manifests and **not applied limit** ranges for the containers. As an attacker, we can **consume all the resources where the pod/deployment running** and starve other resources and cause a DoS for the environment.