-
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
Potentially unreliable feature extraction on ELF sample #1268
Comments
Sometimes it does though?! I'm pretty sure I saw runs where vivisect worked... |
i haven't seen it work on my machine, but if it's an issue of timing or something, that's maybe not surprising. if you can try a few more times and confirm that it sometimes works then i'll dive more into viv. |
it seems like the emucode analyzer is supposed to work here. digging into why it doesn't work as expected. |
Interesting! No match on new workspace every time:
Match, when resusing existing workspace!?
|
All exported features for a run that includes |
This comment was marked as outdated.
This comment was marked as outdated.
root cause reported upstream. we'll be blocked on viv here, unless we want to introduce our own viv passes with capa to better handle things like this. |
When running below rule on 294b8db1f2702b60fb2e42fdc50c2cee6a5046112da9a5703a548a4fa50477bc vivisect sometimes extract the
localtime
api feature and sometimes it doesn't. Is there a bug in the extractor, vivisect, or elsewhere?ref: mandiant/capa-rules#654
The text was updated successfully, but these errors were encountered: