forked from cliffe/SecGen
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathflawed_fortress.xml
More file actions
255 lines (223 loc) · 8.23 KB
/
Copy pathflawed_fortress.xml
File metadata and controls
255 lines (223 loc) · 8.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
<?xml version="1.0"?>
<scenario xmlns="http://www.github/cliffe/SecGen/scenario"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.github/cliffe/SecGen/scenario">
<name>Flawed Fortress</name>
<author>Z. Cliffe Schreuders</author>
<author>Thomas Shaw</author>
<description>A three VM full day intermediate CTF, with a range of challenges of various difficulty.
The three VMs are not related to each other.
We have used this to host events with university students.
</description>
<type>ctf</type>
<type>attack-ctf</type>
<type>pwn-ctf</type>
<difficulty>intermediate</difficulty>
<CyBOK KA="AC" topic="Symmetric Cryptography">
<keyword>symmetric encryption and authentication</keyword>
</CyBOK>
<CyBOK KA="F" topic="Artifact Analysis">
<keyword>cryptographic hashing</keyword>
<keyword>Encoding and alternative data formats</keyword>
</CyBOK>
<!-- remote vuln -->
<CyBOK KA="MAT" topic="Attacks and exploitation">
<keyword>EXPLOITATION</keyword>
<keyword>EXPLOITATION FRAMEWORKS</keyword>
</CyBOK>
<CyBOK KA="SOIM" topic="PENETRATION TESTING">
<keyword>PENETRATION TESTING - SOFTWARE TOOLS</keyword>
<keyword>PENETRATION TESTING - ACTIVE PENETRATION</keyword>
</CyBOK>
<!-- escalate to user and to root -->
<CyBOK KA="AAA" topic="Authorisation">
<keyword>Elevated privileges</keyword>
</CyBOK>
<CyBOK KA="AB" topic="Models">
<keyword>kill chains</keyword>
</CyBOK>
<CyBOK KA="MAT" topic="Malicious Activities by Malware">
<keyword>cyber kill chain</keyword>
</CyBOK>
<!-- a large scenario -->
<system>
<system_name>attack_vm</system_name>
<base distro="Kali" name="MSF"/>
<input into_datastore="IP_addresses">
<network_ip system="attack_vm"/>
<network_ip system="decode_me"/>
<network_ip system="in_the_wild"/>
<network_ip system="that_escalated_quickly"/>
</input>
<utility module_path=".*/parameterised_accounts">
<input into="accounts">
<value>{"username":"kali","password":"kali","super_user":"true","strings_to_leak":[],"leaked_filenames":[]}</value>
</input>
</utility>
<utility module_path=".*/iceweasel">
<input into="accounts">
<value>{"username":"kali","password":"kali","super_user":"true","strings_to_leak":[],"leaked_filenames":[]}</value>
</input>
<input into="autostart">
<value>false</value>
</input>
</utility>
<utility module_path=".*/kali_top10"/>
<utility module_path=".*/kali_web"/>
<network type="private_network"/>
<input into_datastore="spoiler_admin_pass">
<generator type="strong_password_generator"/>
</input>
<build type="cleanup">
<input into="root_password">
<datastore>spoiler_admin_pass</datastore>
</input>
</build>
</system>
<!--some basic decoding challenges-->
<system>
<system_name>decode_me</system_name>
<base platform="linux" type="server"/>
<!-- comment describes using pseudo code (C#-like methods with named optional arguments) -->
<!-- vulnerability_nfs_share_leak(strings_to_leak: encoder_flag_generator() CONCAT encoder_ascii_reversible(strings_to_encode: encoder_flag_generator()) CONCAT ...) -->
<vulnerability name="NFS Share Leak">
<input into="strings_to_leak" unique_module_list="unique_encoders">
<generator type="flag_generator" />
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
<encoder type="alpha_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
</input>
</encoder>
<encoder type="alpha_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
</input>
</vulnerability>
<network type="private_network"/>
<build type="cleanup">
<input into="root_password">
<datastore>spoiler_admin_pass</datastore>
</input>
</build>
</system>
<!--a few vulnerabilities that are in the wild, with some flags that need decoding, some red herring services to keep things interesting-->
<system>
<system_name>in_the_wild</system_name>
<base platform="linux" type="server"/>
<vulnerability read_fact="strings_to_leak" access="remote" privilege="user_rwx">
<input into="strings_to_leak">
<generator type="flag_generator" />
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
</input>
</vulnerability>
<!--double encoded-->
<vulnerability read_fact="strings_to_leak" access="remote" privilege="user_rwx">
<input into="strings_to_leak">
<generator type="flag_generator" />
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<encoder type="ascii_reversible">
<input into="strings_to_encode">
<generator type="flag_generator" />
</input>
</encoder>
</input>
</encoder>
</input>
</vulnerability>
<!-- vulnerability which can leak images, leak 2 image challenges and a random red-herring image -->
<vulnerability read_fact="images_to_leak">
<input into="images_to_leak">
<generator read_fact="strings_to_leak" type="image_generator" >
<input into="strings_to_leak">
<generator type="flag_generator" />
</input>
</generator>
<generator type="image_generator"/>
<generator read_fact="strings_to_leak" type="image_generator" >
<input into="strings_to_leak">
<generator type="flag_generator" />
</input>
</generator>
</input>
</vulnerability>
<vulnerability read_fact="strings_to_leak">
<input into="strings_to_leak">
<generator type="flag_generator"/>
</input>
</vulnerability>
<service/>
<network type="private_network"/>
<build type="cleanup">
<input into="root_password">
<datastore>spoiler_admin_pass</datastore>
</input>
</build>
</system>
<!-- an example remote storage system, with a remotely exploitable vulnerability that can then be escalated to root -->
<system>
<system_name>that_escalated_quickly</system_name>
<base platform="linux" type="server"/>
<vulnerability read_fact="images_to_leak" access="remote" privilege="user_rwx">
<input into="images_to_leak" >
<generator read_fact="strings_to_leak" type="image_generator" >
<input into="strings_to_leak">
<generator type="flag_generator" />
</input>
</generator>
<generator type="image_generator"/>
</input>
<input into="strings_to_leak">
<generator type="flag_generator" />
<generator type="ctf_challenge" />
</input>
</vulnerability>
<vulnerability read_fact="strings_to_leak" access="local" privilege="root_rwx">
<input into="strings_to_leak">
<generator type="flag_generator" />
</input>
</vulnerability>
<service/>
<network type="private_network"/>
<build type="cleanup">
<input into="root_password">
<datastore>spoiler_admin_pass</datastore>
</input>
</build>
</system>
</scenario>