| @stardevreal patching (that is, changing the code/the executable) is not allowed on crackmes unless explicitly stated. That is literally in the website FAQ. |
4:55 PM 12/12/2025 |
==> |
| Here are some known solutions to this crackme (solutions with invalid ascii characters will be written in hex):
"4530395016" (shout out to nightxyz for discovering this one)
"Hashed Password" (originally used to generate the hash)
"c{nnwc" (generated by my mobile phone in less than a secound without using brute force!! (check writeup for more details))
(hex) 02 10 09 02 1D 15 0D (also generated by my mobile phone in less than a secound, and also without brute force)
(hex) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c6 14 40 00 (abuses the buffer overflow to, from auth, return to grant_access instead of returning to main (check the crackme's source code))
|
3:03 PM 08/18/2025 |
==> |
| Guys, I'll make it clear that the intended method to solve the crackme is not brute force! Please instead try to find the vulnerability in the code instead involving a buffer overflow. |
2:57 PM 08/18/2025 |
==> |