For this year's crypto challenge we have 3 stages, but it's on a server which is receiving a lot of empty UDP packets and it sometimes reboots without notice, very strange, but IT tells us they are working on it ... Here is how you access the API to query the oracle, good luck!
All challenges can be queried on the API under https://cryptochall.ks.kgc.io (N.B. it refuses insecure connection). Any submitted characters not in [a-zA-Z0-9 ] will generate an error.
To solve the first 2 challenges, you must write a program that creates valid signatures, in order to send the /win endpoint the message specified in the /flag one. That signed message must be successfully verified by the verification service. Obviously, your program should not just copy a signature received from the signing service, and we've thus blacklisted the winning messages.
The 3rd and final challenge is won by decrypting the flag.
Denial of Service and bypassing the API is prohibited and not part of the challenge.
Prizes have to be claimed at our "Kudelski Bash" party held at the Foundation Room Lounge in Mandalay Bay, Tuesday August 7th between (6-9pm) before the Black Hat briefings. We have five Ledger Nano S hardware wallets along with approximately $100 USD in ETH for you to win.
Can't complete all 3 challenges? That doesn't mean you shouldn't participate, in the event that there aren't 5 people able to complete all 3 challenges the remaining prizes will go to the first runners-up to complete 2 of the 3.
The ranking is established on the time of your submission to the email address provided.
Please include your code and scripts, as well as a (short) write-up explaining your attack. You must submit a response after each one of the challenges is completed. Please use the following subject lines for the email.
Include in your message whether or not you'd like your name (or nick) to be published below in our ranking table.
Your submission can be sent to our email address cryptochallenge@kudelskisecurity.com.
You can encrypt your message, or attachments, using the following public key:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQENBFszjFEBCAC3xFJpb4/zJ9y0VxtKgkBcb0Qiow1xhLN+8dQNH08pUrULDjXu
9XNM/ejDFMEHHDMAYG4xnQB/tXaHjiX4+OeUKAp8IOhMQhgzRi/ceZWYEcSBVeTw
7juUoSuI1ixKLLSdrr+amNtHwpP1hCa7JgMWTf+Brq1PZ2f+5sJ8mSzeIpC9ak6k
t88QfNhXKBvEm5lmoT0jIn3np906M6t6b5rcTPtembEhGfHb9vmzKGvPM13IRhDy
w2S2wn1doPCYlNLJtlVw9Iidt8pQ5zJDpnXaxfnsc3zSjYbJvG5NIkLSXzbqavEK
TnG4OY2dor+nk9yuwMWQRv/18LkeydFabB0LABEBAAG0SEt1ZGVsc2tpIFNlY3Vy
aXR5IENyeXB0b2NoYWxsZW5nZSA8Y3J5cHRvY2hhbGxlbmdlQGt1ZGVsc2tpc2Vj
dXJpdHkuY29tPokBPQQTAQgAJwIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUC
WzXr/AUJAEL5KwAKCRDZeM53RBdstkpLB/0aPa44QxNPaY8W/INgRMs3MRDNM+7Q
vBYoqOr9IeDilpqUCGnnw+UiZHuJXzgW66Dh/Fn2IJYHzDOY0SzXcPwCnVfRoqtU
+5UK6cXY83Y+Si45feJ7k17I2p9EllkTC5czwStFjEW0REbQeN6g31ZkHEiebiYU
izO33UivbSiFKiNDUM/iiJ0HHT6rogVtWkM5bUDeVf9wyQAqUKUaZt1SoX4jkDcw
+CRA8261g3J6tkAKHnDHwK0Zv+NcaGV7RLi0Rl0gIue8t3ZDjKy09wwgoFjlqJG6
6kP0kw5dL5Tp1PLS/ECzaBAb+OEx6YW2cfWbw6KQKXpvbIh04+U18cbhuQENBFsz
jFEBCADaR5wHUVOtzwzOoTp1X5dsvojnG6/9UIn+Z/+5tJFZkxLs0CkBMPtEjR//
39n5jqRi6/iTcVNE+5UvJKny8Z/U8EN1ClcmlDqtwSI+7uqdxvFaSyqUhHy5ihnh
QC4W+n8/eCVWI07t8nDjad4Fd+rhdcSw8CW2FZkhxAA4iiL38MTzaydIhvJzAix4
x8AFh0vSNPUaaRjJoTt+sb9COrCuOyHYncHZV3w20gTNCSIXHiEBVrWIFwCYoaMZ
ThUbz5f0tMlS/lkXPIWc1CLFJs2ZbRAT6u840yV2dJ8zmHdQMC8kb3sRUKQfPkON
ayZAhIkxj0adeaUgGzd/UeZfzW0HABEBAAGJASUEGAEIAA8CGwwFAls17BwFCQBC
+UsACgkQ2XjOd0QXbLaM8ggAnjD0ROpTas/2tN1/q2RXKALGCAbhcg7pL9FP8Kcl
7BuVZQ7qndcutKuN5ppJz96Xf+W0feNRY8+qTAOVayImpzfA1NjQQBOx+MNvJWOT
E91CK/mEWVticTH5ercb8NwYnCF8+ZdKWn4hnfzfVoKcVOmJuAptfbzLoHhmhrpA
7UAt1MxPs1frh9RTcwn6yehvTxv7rVeURQsE8SK0L3JSqZ4AsNjGlD3RtBhrOKIG
dw/Yb38zHjx/+t5HsOJZhaZPtbWRUI6HaJ3ero5vqw//iPDE0Xw2o5/PV8892AT3
Jzw3VA+2z2MSUhb6U8egYE9uNOwqRBlUBDLR5DjsC2UNKg==
=L/Hh
-----END PGP PUBLIC KEY BLOCK-----This is the ranking, classed by date. Name in bold have solved all 3 challenges, congratulations to them!
| Challenge N° | Validation date | Name |
|---|---|---|
| 1 | 2018-07-24 | Joshua Roys |
| 3 | 2018-07-24 | Stefan Kölbl |
| 1 | 2018-07-25 | @mongobug |
| 1 | 2018-07-25 | Stefan Kölbl |
| 1 | 2018-07-26 | Donjon - Ledger |
| 3 | 2018-07-26 | Donjon - Ledger |
| 2 | 2018-07-28 | Donjon - Ledger |
| 2 | 2018-07-28 | Stefan Kölbl |
| 3 | 2018-07-29 | Adrien Guinet |
| 3 | 2018-07-30 | @doegox |
| 1 | 2018-07-30 | Adrien Guinet |
| 3 | 2018-07-30 | Jérémy Jean |
| 1 | 2018-08-01 | Lucille Tordella |
| 1 | 2018-08-01 | Kévin Szkudłapski |
| 3 | 2018-08-04 | Lucille Tordella |
| 3 | 2018-08-04 | Kévin Szkudłapski |
| 3 | 2018-08-05 | Zeta Two |
| 2 | 2018-08-07 | Adrien Guinet |
| 1 | 2018-08-07 | Zeta Two |
| 1 | 2018-08-17 | Nuno Humberto |
Throughout the competition we may drop some hints, so keep your eyes peeled for those.
Hint 1: The challenges are based on fault attacks and the fault occurs automatically on the server.
Hint 2: The binaries are provided to help you figure out what algorithms are used by the server.
So, we have a implemented one of the latest well-documented signature algorithm to authenticate our messages. It's really cool and secure, you should try it!
We've setup an API to allow you to authenticate the messages you send us.
This challenge has four endpoints available on the API:
/chall1/sign (POST) with one argument data/chall1/verify (POST) with two arguments data and signature/chall1/win (POST) sign the message returned by /flag to win/chall1/flag (GET) get the winning message to signAlright, our previous attempt had a flaw or maybe someone built a quantum computer to break it, we don't know. So we've decided to use post-quantum algorithms now. Attackers can't do anything now.
We've setup an API to allow you to authenticate the messages you send us.
This challenge has four endpoints available on the API:
/chall2/sign (POST) with one argument data/chall2/verify (POST) with two arguments data and signature/chall2/win (POST) sign the message returned by /flag to win/chall2/flag (GET) get the winning message to signThat's awful, asymmetric crypto is completely broken. All our attempts failed, so we resorted to the safest crypto of all time: symmetric crypto. AES128 should be fine for our needs and since the attacker doesn't know the key, they can't do anything!
We've setup an API to allow you to encrypt the messages you want to send us, that should work. But since we don't trust whitebox crypto, we cannot give you the binaries, sorry. It's just plain AES128, with 16bytes blocks, don't worry.
Ah, and to avoid having problems with these strange faults that occur randomly, we've added a nice countermeasure. This time we did our homework. We give you, the unbreakable.
This challenge has two endpoints available on the API:
/chall3/encrypt (POST) with one argument data/chall3/flag (GET) get the encrypted flagNote that in this case, the challenge is won by decrypting the flag. Good luck!