pseudo

Hi guys, I'm stuck with pseudo. I've done few steps ahead but now I'm stuck, watching it just looping on 0x7F. Need to discuss with someone who solved it, it's the last chall I need to finish REing challenges and it's starting to drive me crazy :)

Comments

  • done, nevermind.

  • I have un packed it with the tool which was use by them to pack it.
    And I got a flag like part from it HTB{base64_encoded message}
    But its like fooling, as it was not the flag,
    Please help!!

  • i can't run the file on my kalilinux what can i do i can't even add architecture for it

  • For anyone having issues running this and who don't have access to ARM hardware (like a Raspberry Pi), I found something useful:

    https://blahcat.github.io/2017/06/25/qemu-images-to-play-with/

    The arm64_stretch package ran just fine for me under Kali, right out of the box with no tweaks necessary. Pretty cool. You can transfer files to it over SSH.

    Having said that, has anyone made any progress with this? I'm not familiar with ARM, so I'm having a difficult time.

    opt1kz

  • edited November 2018

    I'm at the point where I know that the executable is a VM executing some "byte code" on a 2-register machine and I've figured out what 8 out of the 12 "instructions" do, but I'm having trouble with the last four. The use of floating point aarch64 instructions is confusing to me.

    Would someone be willing to give me some pointers on how to proceed?

    EDIT: The byte code sort of looks like a modified version of a certain esoteric language.

  • Solved after recognizing similarities to a certain esoteric programming language and writing a custom interpreter that skips a certain something.

    This is probably my favorite challenge out of all the reversing ones.


    Also, in addition to the aarch64 system image @opt1kz mentioned, you can also use qemu's built-in GDB server (qemu-aarch64-static -g <port> ./pseudo), which doesn't require a sysroot because pseudo is a statically linked executable.

  • I was able to run the code both with an actual device and with qemu, but how can you debug this? gdb doesn't have symbols so I can't setup breakpoints, while radare2 says "Sorry. No debugger backend available." when launching in debug mode.
    Anyway with radare2 I'm able to see the assembly code (which for me seems pretty crazy).
    Did you solve it without debugging?
    This is my last retro, it seems very interesting but I am probably missing something XD

    mrlbender

  • radare2 says "Sorry. No debugger backend available." when launching in debug mode.

    I'm not super familiar with radare2. Does it let you connect to a gdbserver? I used qemu-aarch64-static -g 12345 ./pseudo to start a gdbserver and set up IDA to connect to a remote GDB server at <linux VM's IP>:12345.

    Did you solve it without debugging?

    Yep. I only used the debugger to find approximately where the interesting stuff was and then worked off the disassembly.

  • Yes radare allows you to connect to a gdb server, but I have never tried it yet. I was using gdb directly, it connects but got some errors (code is running but can't setup breaks).
    Anyway thank you for your answer!!
    I will try to look better at the code :)

    mrlbender

  • Finally did it, thanks for the help!
    Eventually using qemu and radare2 + a script in python I wrote :)

    mrlbender

  • I've gotten to the point where the program is executing the loop based on bytes and see where and how the input is being stored. I'm stuck at this point and could use a push in the right direction.

  • Hi How many zip files appear before it reaches the end?

  • Hawkeye16 - you are on good track - now try to find other loops in the arm code where user input is used.

  • btw few people wrote me for hints on PM, and I'm glad to help out, but I honestly expected a "respect" at least. I'm not being salty for a game but it's just I'm a bit disappointed since it's not that fair to ask for an hint and do not give something back. Please consider this before writing me :)

Sign In to comment.