-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NASHTA fails disassembly #69
Comments
I think I see what might be happening here. |
I got the assembly with a command similar to Are you sure the bug is in gtirb-pprinter and not from ddisasm? Ddisasm could rely on gtirb-pprinter after all. |
Will somebody fix it or should I open a PR please? |
on the same binary I also have I would like to edit:
because it is the only moment where ImageBase is present in the text file. @aeflores If you think this is not related to ddiszasm / gtirb dev, could you send me an email please? |
Ddisasm uses gtirb-pprinter as a library to generate assembly, so yeah this is a pprinter issue. Regarding ImageBase, I think we define this as an external symbol so it can be defined by the linker when reassembling. |
Should I set ImageBase from compile command option like /imageBase, remove the variable or something in order to fix it please? |
If I set /base 50000 remains the undefined symbal ImageBase. |
The commit f6bea62 fixed the undefined externs (imports). I checked that the resulting assembly successfully reassembles, the |
great! I will test this week. |
I am confused. could you provide the full command please? |
It has been a while, but the following should work
|
should it work with --asm option as well please? |
nashta.zip
Please provide as much of the following information as possible:
I had to patch the disassembled asm to remove section permissions in order to avoid compilator error. I also change the INCLUDELIB keyword arguments. Then, on this file, I did:
I can not recompile the new disassembled file due to the previous error.
I have not sent the nashta malware in order to avoid to infect people by accident. I let the hash in the name instead. Could you ask me in person in order to disassemble it if you do not found it please?
The text was updated successfully, but these errors were encountered: