===================== 01 : [game] sorry, / 05-24 13:48:01 ====================== We appologize for the inconvenience. The binary of 'game' has been replaced. Please refer to the challenge page. ============== 02 : [bigfile of secret] hint !! / 05-24 14:31:27 =============== Range: bytes ================== 03 : [127.0.0.1] hint !! / 05-24 15:41:15 =================== the ports to need to solve this challenge. (TCP) 21, 3132 ========== 04 : [127.0.0.1] we added a mirror server / 05-24 17:55:33 ========== as some ppl claim that they can't connect the [127.0.0.1] server, we added a mirror server . refer the challenge page. ================== 05 : [debugd] ip changed / 05-24 18:36:05 =================== changed to 115.86.51.180 refer the challenge page =============== 06 : [debugd] ip changed again / 05-24 19:23:41 ================ changed to 115.86.51.180 refer the challenge page (sorry,) =========== 07 : [toolbox] the OS of the challenge / 05-24 22:01:28 ============ OS : ubuntu 13.04 32bit ======= 08 : [debugd] this challenge is available now.. / 05-24 22:57:45 ======= => sorry, binary is changed to fix problem..! Binary : http://war.secuinside.com/files/debugd2.zip IP : 54.214.248.2 PORT : 7744 ====== 09 : [givemeshell] more ports for this challenge / 05-25 00:06:17 ======= we opened more ports ip : 119.70.231.180 port : 8761, 8762, 8763, 8764, 8765 ============= 10 : [oldskewl] hash collision issue / 05-25 01:03:34 ============ [hint] the key is consists of english words you had better use dictionary file to find the intended words ======== 11 : [banking] warning to user 61.107.162.18 / 05-25 03:32:31 ========= 61.107.162.18 don't do like that. banking websocket connection is full every minute cuz your dummy connection. (yep, we know that this connections are not for ddos. but it is harm.) just slow down. =================== 12 : [banking] hint !! / 05-25 04:33:21 ==================== 1. you don't need to know other user's password. 2. flag is in database. but, it's not in user table. =========== 13 : [oldskewl] hash collision issue 2 / 05-25 07:03:49 ============ The answer words are quite common words. The dictionary file we confirmed working was the basic one from BackTrack5. (/pentest/passwords/wordlists/darkc0de.lst) If your dictionary file does not work, you might want to use that file. ==================== 14 : [debugd] hint !! / 05-25 08:20:24 ==================== :: FORMATSTRING :: ========= 15 : [pwn me] we have added one more server / 05-25 09:55:57 ========= - new mirror server - IP : 54.214.248.112 PORT : 8181 for the stable traffic. ====== 16 : [secure web revenge] some more modification / 05-25 10:32:36 ====== we have modified the upload.php to prevent not intended attack please check the changed upload.txt! ===== 17 : [secure web revenge] challenge closed. (sorry) / 05-25 12:25:04 ===== sorry, secure web revenge module has a some other bug.. this challenge will be reopen after fix. ============== 18 : [trace him] Point is changed / 05-26 02:17:09 ============== Point of "trace him" is chaged to 850 ============= 19 : [xml2html] information updated. / 05-26 04:45:47 ============ Good luck. ============= 20 : [pwnme] we added a new server. / 05-26 06:00:02 ============= sorry, as we realized there is some different OS environment from ours we added a new server. =================================== OS : Ubuntu 13.04 with PIE+ASLR+NX md5 of libc-2.17.so : 45be45152ad28841ddabc5c875f8e6e4 IP : 54.214.248.68 PORT : 8181,8282,8383 IP : 54.214.248.112 PORT : 8181,8282,8383 IP : 54.214.248.97 PORT : 8181 =================================== OS : Ubuntu 13.04 with PIE+ASLR+NX md5 of libc-2.17.so : 175ce77c05f89f38ad236c2b7b749268 IP : 119.70.231.180 PORT : 8181, 8282, 8383 =================================== ========= 21 : [secure web revenge] about flags file. / 05-26 09:16:12 ========= same to [secure web] flag file name. [secure web revenge's flag file name] = [secure web's flag file name] =================== 22 : [xml2html] NX issue / 05-26 10:10:51 ================== [NOTICE] NX is enabled by default. But we are just noticed that there is some reason that NX won't be enabled in some specific situations like when you run it in VM (depends on VM configuration.) So, NX in our server doesn't work properly. We're releasing this information because we're worried that some teams are working on solving this challenge in NX enabled correctly. and we're sure that you can solve the challenge in both ways, on NX enabled and NX disabled. ================== 23 : [zombiemanager] advice. / 05-26 10:50:35 =============== Be advised. zb.db is being reset time to time. I wish nobody wastes time during exploitation because of this.