-
Notifications
You must be signed in to change notification settings - Fork 570
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
Recent capa version don't work with sample dumped from memory #2580
Comments
It appears that something broke when we upgraded Vivisect from version 1.1.1 to >= 1.2.0. Vivisect 1.1.1:
Vivisect 1.2.1:
I'm not sure of the issue source. It could be a change to Vivisect between 1.1.1 and 1.2.0 or something that we didn't change in capa and/or viv_utils to accommodate the Vivisect changes. Running show-features.py for the function 0x401635 tells us that capa isn't seeing a majority of the instructions/basic blocks when using Vivisect 1.2.1 versus Vivisect 1.1.1: Vivisect 1.1.1:
Vivisect 1.2.1:
|
there are lots of warnings during viv workspace creation, and the addresses seem to line up with functions/instructions above: the logging message is here: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
by manually bisecting the changes, here's the offending viv commit: |
this was added in vivisect/vivisect#622 |
Description
I have dumped the UPX packed sample
a27afd3ec5b3f2e705347b2c39847fcd659e430396abd081109db0e7f96d1d3e
from memory using pd64. capa 7.3-8.0 does not detect any capabilities in the dumped sample, while capa 7.0-7.2 does.I wonder why capa does not detect the capabilities of this sample in the newer versions and if we can fix it.
capa 7.3-8.0 does detect capabilities on the UPX unpacked version (unpacked using
upx -d
after renaming the sections).Steps to Reproduce
a27afd3ec5b3f2e705347b2c39847fcd659e430396abd081109db0e7f96d1d3e
pd64 -pid <PID>
Versions
capa 7.3-8.0 standalone tool.
The text was updated successfully, but these errors were encountered: