Vector35 / Vector35/binaryninja-api
Null pointer deref when loading DYLD Shared Cache image using an address
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- C++
- Estrelas
- 1.3k
- Forks
- 298
- Merge médio
- 5d 5h
- PRs com merge (30d)
- 19
Descrição
Version and Platform (required):
- Binary Ninja Version: 5.3.9429-dev Ultimate (ea9c02c3)
- Edition: Ultimate
- OS: macOS
- OS Version: 26.4
- CPU Architecture: M1
Bug Description:
I attempted to load a DYLD Shared Cache image via the UI using the Load Image by Address right-click option. When I hit enter to load the address Binary Ninja crashed.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- Load a copy of DYLD Shared Cache. In my case this was 26.2 for an iPhone 17 Pro Max
- Wait for initial analysis to complete
- Shortly after right-click linear view and select
Load Image by Address - Press enter on a pre-populated value. I had loaded by that address on previous runs so its pre-populated in the text box so I just hit enter after the text box appeared
Additional Information:
It doesn't happen everytime. I'm kind of just hoping that the crash file is enough to diagnose the issue as it looks pretty shallow.
Crash dump: civic ward replicates proudly
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Start with the reported macOS M1 reproduction: load the iPhone 17 Pro Max DYLD Shared Cache, wait for analysis, then use Load Image by Address with the pre-populated value. Review the crash dump identified as “civic ward replicates proudly” and compare repeated attempts, since the failure is intermittent. Done means the image loads through this UI action without a crash.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- cpp, macos
- Domínio
- operating-systems, reverse-engineering
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 42/100