Number of crackmes:
Number of solutions:
Comments:
| Name | Author | Language | Arch | Difficulty | Quality | Platform | Date | Solution | Comments |
|---|
| Crackme | Infos |
|---|---|
| Small Keygenme | nice crackme target, a "you must try it" for beginners |
| timotei crackme#3 | No need for brute forcing |
| timotei crackme#4 | my solution, more than 1 password, 1 useable from commandline. I suggest to at least reverse engineer the program. |
| timotei crackme#2 | message to beginners: First try it yourself, it isn't that difficult. This was a nice reverse engineering practice. There are more solutions but someone ust use his brains and read carefully the code. As long as the first and the last character of the password is right.... pass. That's all I'm gonna tell. |
| Personal Safe | Here's my solution to the problem. It was nice. |
| j444 by josamont | Nice crackme for beginners, it's very easy but not so 'very'. Beginners can learn from it. (as from other crackmes ofcourse) |
| j333 by josamont | difficult to debug with Evan's Debugger, it just don't let you to give some input. Also a surprise was that there aren't .text,.data,.rodata sections present. I have some homework to do now to know how I can do this. |
| basic_logic by eholzbach | Not really very easy problem, impossible to guess the password without reading and interpreting the code (but that was the goal), Thanks to kaltwa55er I learned how to deal with the input problem and I found an error on my website thanks to this crackme. |
| easy_linux_crackme by lord | full explanation with patching the (copy of) original binary file. No debugger needed. Nice usergroup id by the way (in hexadecimal it's a readable word) |
| easy_crackme_2 by lord | Quite very easy as long as you can read and understand assembly language and knowledge of ASCII. I checked with a debugger. |
| crackme_nasm by rezk2ll | easy one, just assembly code reading |
| crackme-not | cracked with objdump, reading assembly code and finally edb debugger. (sudo apt install edb-debugger should do the trick on Ubuntu like systems) |
| Lucky Numbers | This is a quite long explanation of how I did it. Took a while because of the DAA instruction. |
| nasm crack | Very easy one |
| EZ crackme | hexdump -C run.exe reveales: 00002000 50 34 35 35 77 30 72 64 59 6f 75 20 47 6f 74 20 |P455w0rdYou Got | 00002010 54 68 69 73 21 0a 57 72 6f 6e 67 21 0a 1c 00 00 |This!.Wrong!....| most probably it must be P455w0rd using gdb (I've used Evan's Debugger so more easy) gdb ./run.exe set args P455w0rd run the response: You Got This! [Inferior 1 (process 27562) exited normally] |
| Comment | Link |
|---|---|
| second attempts to upload my solution, this time no bruteforce but mathematical solution.... | ==> |
| Nice challenge, didn't took long but long enough to call it level 2 worthy. | ==> |
| cracked. There are more pincodes possible... | ==> |
| Here my (long) solution, wait unpacking the zip until you at least try to reverse engineer the program. I've got more than one valid passwords with one useable on commandline. | ==> |
| ups, wrong hit, it's a hint for timo#2, sorry. | ==> |
| Here is a hint: it's ROL nor SHL | ==> |
| However any program is assembly language, this one should be in the C/C++ section of the site. | ==> |
| This was a nice one. Took 45 minute to decipher the algorithm, 30 minutes to find out that there is no single solution. Still don't know why exit must be in a subroutine. | ==> |
| A bit more difficult than j333 but with the source code and some reading.... also look at the decimal ascii to hexadecimal conversion (to check the digits), another hint SUB.... instead of first CMP and then SUB. No section headers so use ghydra, objdump..... | ==> |
| This is a fairly easy once you've have the assembly listing. I encourage beginners to not look at the answers and try it yourself. You will llearn a lot. | ==> |
| Nice andsimple example for a beginner to get started with patching/modifying binaries. I suggest beginners to stay in command line and try not to use a debugger.... | ==> |
| This was an easy one with a debugger. | ==> |
| No need for a debugger, just a disassembler (objdump in my case and assembly code reading plus ASCII table. Not a difficult one. Password seems longer than it actually is. | ==> |
| Nice example, no bugs but lot of distractions (for beginners at least). there is a password length and not all input is OK, not gonna reveal it in this comment. Wurth trying. | ==> |
| The DAA instruction put me in a difficult position since CF can be 1 at start. I presumed that lucky numbers implicitly means numbers so I stuck with 0...9 as input. The solution was easy found after this. Nice example. | ==> |