Closed bugfinder-bot closed 2 months ago
/cib
Some functions will not generate a MLIL because of internal binary ninja errors. ==> Check if property MLIL is present for a given function before trying to parse it. ==> Throw ValueError at CFG creation
Also we use BinaryViewType
which should only be used internally to create a binary view.
==> Exchange function to load
which should be the default for version 3.5.
Another thing closely related to this kind of problem:
analysis.mode
to intermediate
instead of full
which will be a bit faster for larger binaries. Again 3.4 is kinda weird with this flag, some functions are not detected properly (not in the API, but in the GUI) ==> 3.5 fixes that for the functions i tested
==> bundle changes together + block until 3.5
Add changes for 3.5 as well in this issue
Change of plan: 3.5 dev does not really work with internal view ==> split into original problem + 3.5 update issue
What happened?
Error class
AttributeError@parser.py:33
contains 14 cases.How to reproduce?
sample: c1d9fea2199334ac7ef38db208c10cbda10e105e9ff748d3c154f56fc455e8e8 case: https://bugfinder.seclab-bonn.de/case/28/ dewolf commit: 84caaa95 Binaryninja version:
3.4.4271