Vector35 / Vector35/binaryninja-api
Annotate accesses to unmapped memory addresses
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
It would be helpful when reversing firmware and trying to deduce MMIO ranges, etc. if Binary Ninja could provide a way to find references to unmapped memory addresses.
Furthermore, if it were queryable via the API (which is ideal), then I could do something like this:
bad_pages = set()
for addr in bv.unmapped_addrs_ficticious_api:
bad_pages.add(addr & ~(0x4000 - 1))
for page in bad_pages:
# TODO: Create section for page...
<zznop> But also, I recommend opening an issue because we could probably annotate accesses to unmapped addresses to make them searchable in "Find"
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 reviewing the public API surface and the existing Find/search behavior described in the issue. Determine how unmapped memory accesses could be exposed both as queryable addresses and searchable annotations. Done means firmware analysis can identify these accesses and use the API to enumerate their addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100