Vector35 / Vector35/binaryninja-api
Analysing sepOS MachO produces incorrect output
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 4.0.4902-dev
- OS: macOS
- OS Version: 14.0, Sonoma
- CPU Architecture: M1
Bug Description:
Trying to analyse the attached binary, taken from an iOS 15.8(.1 maybe?) sepOS image, results in incorrect output. The code begins at around offset 0x1240, but the majority of the data is left in hex format.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- Open the attached binary in Binary Ninja
- Use the default options (mac-armv7) and begin the analysis
- Go to the beginning of the code and observe the disassembly
Expected Behavior:
Readable output, similar to that of IDA Pro (see screenshots for example).
Screenshots:
Binary:
sepdump13_sks.zip
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 by opening the attached sepdump13_sks.zip binary in Binary Ninja with the default mac-armv7 options, then inspect the disassembly around offset 0x1240 and compare it with the supplied IDA Pro screenshots. Determine why most of the data remains in hex format and verify that analysis produces readable output for the provided sepOS image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100