Closed michaelweiser closed 4 years ago
These kinds of backtraces are all follow-up errors to underlying errors masked by cuckoo running peepdf in sloppy mode. This cannot be changed through configuration.
This particular one and its colleagues should be fixed by scVENUS/peepdf#1, also reported upstream at jbremer/peepdf#9.
Research in cuckoo by @Jack28 reveals that static analysis can be disabled completely but not selectively for only peepdf. So it's an all or nothing workaround. To make this more granular, the cuckoo code needs to be patched.
Closing this for now as nothing-we-can-do/invalid/wontfix. Anyone feel free to reopen with suggestions how we could improve upon this from the outside.
We have found another sample that triggers a peepdf traceback in cuckoo even with our fixes from jbremer/peepdf#9:
It seems to be a different code path. This needs analysis and fixing in peepdf and perhaps a rethink if we can and should somehow manage to make these exceptions non-fatal for the cuckoo analysis altogether.