Author:
nnxstnt

Language:
C/C++

Upload:
10:17 PM 09/20/2024

Platform
Windows

Difficulty:
5.0

Quality:
4.0

Arch:
x86-64

Description

Second revision of my previous Juggler crackme, which had a cruel race condition, which I did not find during development at the time. Main challenge is circumventing the anti-debugging measures in place. Patching is allowed, but finding the key is the cooler option.

• Comments
• Solutions

nightxyz on 10:13 AM 10/12/2024: Key = {7h3_h4nd_0f_90d_h0v321n9_480v3}

nnxstnt on 7:51 PM 10/12/2024: hey, nice, would you mind posting a solution?

nightxyz on 11:35 PM 10/12/2024: I used X64dbg , ScyllaHide Basic profile. First, i found the point where user key gets. After that, i traced step by step. I bypassed Int 4 trap. I "traced into" every "call juggler_v2.7FF72EDE9860" because "Trace over" failed. After loading all libraries, I continued to stepping. Somewhere in loop, I saw "curly bracket" next some register. The other register shows my entered key first character. I remembered the password structure for first revision of this crackme and I guessed that this crackme has same type password. I executed loop 32 times and write everey character to a paper. Finally it worked. I can't write solution but i solved with this way and a little bit luck :)

You must me logged to submit a solution