Vector35 / Vector35/binaryninja-api
Binary view leak on malformed binary
Open
Nobody has claimed this yet.
Effort: Trivial
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
- Open array_simpl_patched.zip
- Close binary and run
get_memory_usage_info() - Observe multiple 'Active BinaryView objects'
This currently leaks 5 binary view objects, this is true up until 5.0, in 4.2 it only leaked 2 binary view objects.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the leak with array_simpl_patched.zip, close the binary, and run get_memory_usage_info() to observe the active BinaryView count. Trace the malformed-binary cleanup path; done means closing the binary no longer leaves the reported BinaryView objects active, including the differing counts seen in versions 5.0 and 4.2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100