Vector35 / Vector35/binaryninja-api
API layer should enforce limits on Variable's index and storage
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: 5.4 Ultimate
- OS: macOS 26.5
- CPU Architecture: arm64
Bug Description:
Within core, Variable ends up being stored in a representation that only allocates 20 bits for index and 40 bits for storage. If an API user creates variables with values outside of that range, they'll get unexpected behavior. The API should validate that the provided values are within the acceptable range.
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 at the API layer around Variable and inspect how its index and storage values are accepted and represented. Verify the stated 20-bit index and 40-bit storage limits, then add coverage showing that in-range values work and out-of-range values are rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100