Vector35 / Vector35/binaryninja-api
Improve handling of malformed / dsc_extractor.bundle-processed binaries
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Hi,
I have found that these https://github.com/Vector35/workflow_objc/blob/master/Core/AnalysisProvider.cpp#L22-L23 two analyzers raise out-of-bound exceptions.
Used LaunchServices binary extracted using https://github.com/keith/dyld-shared-cache-extractor from arm64 cache.
Will dig into it tomorrow and update the ticket.
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
Start in Core/AnalysisProvider.cpp at lines 22–23 and reproduce the issue with a LaunchServices binary extracted from an arm64 cache using dyld-shared-cache-extractor. Determine which two analyzers raise out-of-bound exceptions for the malformed or dsc_extractor.bundle-processed binary. Done means the affected binary no longer triggers those exceptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100