search

angr / angr-targets

This repository contains the currently implemented angr concrete targets.
32 stars 9 forks source link

Symbion's test packed_elf_x64 avatar No Memory range specified at 0x400cd6 #10

Closed visionius closed 3 years ago

visionius commented 3 years ago

As I issued in #8 First I commented these three lines in /avatar2/protocols/gdb.py: line:270

self._gdbmi = pygdbmi.gdbcontroller.GdbController()
#gdb_path=gdb_executable,
#gdb_args=gdb_args,
#verbose=True)

I used manual_concrete_packed_elf64.py file and pass the binary file that is available in angr-symbion blog. But the concrete execution is not sync to symbolic state... I don't know the changes that I have been done to that code was the reason or not, exploration can't find the symbolic path and I have avatar No memory range CRITICAL error. ubuntu x86_64 python3.6 angr and angr-target successfully installed without problems.

shot:

image

degrigis commented 3 years ago

Hey there, sorry for the delay, I'll look into this ASAP!

ringzer0x00 commented 3 years ago

I'm having the same issue, tested it with both gdb 10.1 and 8.2.1, assuming it could have been some older protocol implementations in the avatar-based scripts. Apparently it isn't.

ringzer0x00 commented 3 years ago

Tested a bit the whole thing, as we have the same problem most likely. There seems to be some kind of issue on the protocol level on the reception side when it is dealing with memory-related operations. Running avatar2 tests they fail exactly when reading the response. Not sure about this, but apparently the commands sent are fine.