Vector35 / Vector35/binaryninja-api
Null pointer deref when loading DYLD Shared Cache image using an address
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- C++
- Sterne
- 1.3k
- Forks
- 298
- Ø Merge
- 5 T. 5 Std.
- Gemergte PRs (30 T.)
- 19
Beschreibung
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
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cpp, macos
- Bereich
- operating-systems, reverse-engineering
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100